Skip to main content

​
Overview

Nearly every clinical field in a Connective Health FHIR output is a Coding with three parts:
display is the description as the source provided it, not a lookup from the terminology. It may differ in wording or casing from the terminology’s official display for that code.

​
Code system URIs

Source data identifies terminologies by OID. Each is published as its registered canonical FHIR URI where one exists, and as a urn:oid: URN where it does not.
ICD-9 (International) and ICD-10-PCS Procedure are distinct terminologies from ICD-9-CM and ICD-10-CM Diagnosis above — they use different OIDs. ICD-9 (International) is actively checked when resolving an Encounter diagnosis code. ICD-10-PCS Procedure is mapped defensively for completeness even though no current source field is known to carry that OID; if one ever does, it will now resolve to its correct FHIR URI rather than falling back to urn:oid:.

​
Fallback behavior

Codings under a urn:oid: system are still conformant FHIR, but consumers doing terminology validation should expect not to resolve them against a published code system.

​
Connective Health Panel Classification

http://connectivehealth.io/fhir/panel-classification is a Connective Health terminology, not a standard one. It groups laboratory and diagnostic results into clinically meaningful panels, and is published as an additional coding alongside the result’s own standard coding — never as a replacement. See Observation.

​
Code normalization

FHIR does not permit a code value to contain leading or trailing whitespace, or runs of internal whitespace. Because source data occasionally carries such values, every code is normalized before publication:
  1. Any run of whitespace inside the value is collapsed to a single space.
  2. Leading and trailing whitespace is removed.
  3. If nothing usable remains, the code element is omitted.
When code is omitted this way, the coding is still published with its system and display, so the clinical description is not lost. This is done proactively so bundles remain valid FHIR rather than failing validation downstream.