FHIR R4 in CAIL Health
The shape of clinical resources on the wire
CAIL Health models every clinical resource as FHIR R4. If a payload represents an organization, a location, a clinical pathway, a patient response, an observation, or an aggregate metric, it conforms to the corresponding FHIR R4 resource shape.
Resources you will see
The most common FHIR resource types in API requests and responses:
Coding systems and regional terminology
FHIR coding values come from one of two sources:
- Standard systems (LOINC, SNOMED, ICD-10, RxNorm) where the resource has a canonical international coding.
- Jurisdiction-specific systems for terminology that differs by region, including risk tier codes, provider taxonomy, and wait-time metric codes.
When a value is jurisdiction-specific, the active jurisdiction’s coding is used. See Jurisdictions for how the active jurisdiction is determined.
What is not exchanged in FHIR
Authentication tokens, pagination metadata, alert thresholds, and error envelopes are CAIL-specific contracts, not FHIR resources. See Auth model, Pagination, and Error envelope.