Vital Signs Cross-Country Cross-Language Cross-Paradigm (Demo) IG
0.6.0 - ci-build

Vital Signs Cross-Country Cross-Language Cross-Paradigm (Demo) IG, published by FO. This guide is not an authorized publication; it is the continuous build for version 0.6.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/vital-signs-demo/ and changes regularly. See the Directory of published versions

Use of Profile Hierarchies

How to create and establish a profile hierarchy? Why do we need hierarchies?

Base MustSupport ProfilemustSupport on category, status, effectiveDate, interpretation, ..obligation SHALL handleSingle-Value ProfilemustSupport on valueobligation SHALL handle exactlymustSupport on value.unitobligation SHALL handle equivalentMulti-Value ProfilemustSupport on componentmustSupport on component.valuemustSupport on component.value.valueobligation SHALL handle exactlymustSupport on component.value.unitobligation SHALL handle equivalentBlood PressureBody Weightderived fromderived fromderived fromderived from

On the one hand, we have to describe which attributes are relevant. That includes also the associated obligations. On the other hand, some details are specific to the related content profiles like blood pressure. That differs for example by the fields that must be supported, eg. a single value for body weight, whereas blood pressure requires two components instead.

Another aspect is a specification what kind of obligation is associated. For example, units for measurements can be handled in form of an equivalent, so that internally it can be converted back and forth into/from an internal representation. But the measured values must be handled exactly.