Appointment Health History Form

The Appointment Health History form feature will allow the user to view or modify patients historical health information. For more information, refer Health form History workflow.

For the PUT call, you’ll be sending the exact same data structure back from the original GET, with possible changes to the answers. Each section should have a complete set to true once it is completed by a patient. The various IDs that are not specified in the fielddata hash should be parroted back to the API unchanged; this is how we keep track of the questions. Those IDs are not shared between practices. They are set whenever the portal health history form questions are added or changed.

While it's easiest just to return the entire structure, the minimum to be sent back are the 'portalformsectionid,' 'type,' 'complete,' 'empty,' and 'questions' elements. In the 'questions' elements, you just need the 'fields' (and subelements) and 'portalformquestionid' elements. The exceptions are the MEDICATION and ALLERGY sections, in which almost all elements under 'questions' are required.

Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit
Get list of health history forms for given appointment
Example Code
Get specific health history forms for given appointment
GET
/v1/{practiceid}/appointments/{appointmentid}/healthhistoryforms/{formid}

Retrieves a specific Health history form for an appointment

Was this information helpful? Yes | No Thank you for your feedback! What went wrong? Incomplete or incorrect information | Irrelevant Content | Others
Submit
Try in Postman

Input Parameters

Expand all

Output Parameters

Expand all
Example Code