FHIR Output
Results are available as FHIR R4 in two ways. Both return application/fhir+json, and both take your organization from the access token.
| API | Returns | Scope | Modes |
|---|---|---|---|
| Document Bundle | One document's results as a collection Bundle | batches:read | Test and live |
| FHIR Server | Patient-level reads and searches across your organization's processed documents | A SMART system scope | Live only |
Document Bundle
curl -s \
"https://api.amorphous.health/v1/data-engine/batches/$BATCH_ID/documents/$DOCUMENT_ID/fhir" \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Accept: application/fhir+json"
Available once the document has succeeded. In test mode, the Bundle is built from fixture entities.
If the document has no patient, the Bundle includes a placeholder Patient so that references resolve. The placeholder is not a patient record.
Code Systems
Codes use FHIR system URIs, the same as codes[].system on entities. Other systems can appear, so match on the URI.
| System | URI |
|---|---|
| SNOMED CT | http://snomed.info/sct |
| LOINC | http://loinc.org |
| RxNorm | http://www.nlm.nih.gov/research/umls/rxnorm |
FHIR Server
| Request | Path |
|---|---|
| Capability statement | GET /fhir/R4/metadata |
| Read a patient | GET /fhir/R4/Patient/{patientId} |
| Everything for a patient | GET /fhir/R4/Patient/{patientId}/$everything |
| Read a resource | GET /fhir/R4/{resourceType}/{resourceId} |
| Search | GET /fhir/R4/{resourceType}?patient={patientId}, or POST .../_search with a form body |
| SMART configuration | GET /fhir/R4/.well-known/smart-configuration |
SMART configuration is public. Every other request needs a live token with a system scope for the resource type. $everything needs system/*.rs or system/*.read. See Scopes.