Retrieve Condition
Access a patient's diagnoses, clinical concerns, and conditions from their EHR. This data paints a holistic health picture, vital for care coordination and providing context for ongoing treatments.
To access this clinical data you'll need the patient identifier, obtainable through the Retrieve Patient interaction.
Retrieving the list of conditions can be done by sending a GET request. The request is sent to the Condition endpoint:
https://api.<region>.founda.com/1/organizations/<org-x>/fhir/4/Condition?<parameters>
Where <region> should be defined according to the different Founda regions and <org-x> should be replaced with the Healthcare Provider's organization ID that you are integrated with.
The response contains a Bundle with 0, 1 or N matching Conditions. The full Condition resource can be retrieved with the identifier of the selected Condition from the result set.
Founda adheres to recognized standards (IHE, HL7 FHIR) to ensure compatibility and harmonization among diverse systems. If there is a profile available for an interaction, it is recommended and preferred to follow the prescribed transactions.
The Retrieve Condition interaction with the Founda Platform is based on the IHE QEDm profile. To indicate that the request and response should comply with PCC-44, the _profile parameter should be included to the search set: .../Condition?_profile=https://profiles.ihe.net/ITI/QEDm.
In order to comply with the PCC-44 transaction, the interaction should at least support the parameter in the table below. Additional search parameters, as defined in the FHIR Condition resource, can be used as well.
Parameter | Type | Required* | Description |
---|---|---|---|
patient | reference | | The patient to retrieve the Condition overview for |
patient + category | reference + token | | The patient to retrieve the Condition overview for + the category name of the resource |
patient + clinical-status | reference + token | | The patient to retrieve the Condition overview for + the clinical status (which can be active, resolved, or inactive) |
*At least one of the combinations has to be supported