The HSPC Sandbox is taking steps toward supporting FHIR profile storage, retrieval and validation. Along with this effort comes the storage/hosting of the terminology necessary to accommodate the profiling features. In this blog post I will outline the upcoming features related to profiles, along with some examples of how these features can be useful in the development of SMART on FHIR apps. The efforts are currently focused on support for FHIR STU3, and all examples and documentation are using this FHIR version.
...
Terminology is at the heart of all FHIR resources. Because of this, we've dedicated a sandbox in the HSPC Sandbox Reference API to the storage and retrieval of terminology. This sandbox conforms the FHIR specification of a Terminology Service, and can be used by clients to "...make use of codes and value sets without having to become experts in the fine details of code system, value set and concept map resources, and the underlying code systems and terminological principles." (source). The HSPC Sandbox Terminology Service contains more than 631,310 concepts and relationships, broken down as follows:
- SNOMED CT International RF2 (336,893 concepts)
- LOINC 1.61 (111,803 concepts)
- HL7 v2 & HL7 v3 codes backing FHIR v3.0.1
...
A slightly more advanced use of the $validate operation would be to verify that property values are a member of the correct value set. Let's return to using our example value set, administrative-genergender. The FHIR Patient resource specifies that the Patient.gender field MUST be one of the values in this value set. Let's post a validation request containing the value "incorrect" for gender and see what happens.
...