ValidatePatientManagement in PatientView
A documented PatientView operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
validatePatientManagement
- POSTChanges data · patient-management-controller
www.patientview.org/patientmanagement/validate
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which PatientView operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other PatientView operations
- SavePatientManagementPOST · changes data
- SavePatientManagementSurgeriesPOST · changes data
- Get Observations of Multiple Types For a UserGET · reads data
- Get Basic User InformationGET · reads data
- Get Available Observations Types For a UserGET · reads data
- Get Available Patient Entered Observations Types For a UserGET · reads data
- GetPatientManagementDiagnosesGET · reads data
- GetPatientManagementLookupTypesGET · reads data
Questions
- Can HumDay validatepatientmanagement in PatientView?
- Yes. This operation is published in PatientView's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my PatientView data?
- Yes — this is a POST operation, so it changes something in PatientView. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your PatientView account.
Where this came from
Read from a published API description for PatientView at www.patientview.org/api/api-docs. The description above is the provider’s own wording, not ours. Last published 2020-01-07.