Retrieve Diagnostic Report
Retrieve findings and interpretations of diagnostic tests from patients. Access clinical context, atomic results, images, textual and coded interpretations, and diagnostic report formats. Ideal for accessing a comprehensive view of a patient's diagnostic history.
To access this clinical data you'll need the patient identifier, obtainable through the Retrieve Patient interaction.
Retrieving the list of diagnostic reports can be done by sending a GET request. The request is sent to the DiagnosticReport endpoint:
https://api.<region>.founda.com/1/organizations/<org-x>/fhir/4/DiagnosticReport?<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 Diagnostic Reports. The full DiagnosticReport resource can be retrieved with the identifier of the selected DiagnosticReport 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 DiagnosticReport 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: .../DiagnosticReport?_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 DiagnosticReport resource, can be used as well.
Parameters combination | Type | Required* | Description |
|---|---|---|---|
patient + category | reference + token | | The patient to search data for + the category name of the resource |
patient + category + code | reference + token + token | | The patient to search data for + the category name of the resource + the code of the resource |
patient + category + date | reference + token + date | | The patient to search data for + the category name of the resource + the date of creation of the resource |
patient + category + code + date | reference + token + token + date | | The patient to search data for + the category name of the resource + the code of the resource + the date of creation of the resource |
*At least one of the combinations has to be supported
