Vital Signs Cross-Country Cross-Language Cross-Paradigm (Demo) IG
0.6.7 - 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.7 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

What is the current situation? 2 Level Profile Hierarchy!

Currently we have a two level hierarchy: A base profile describes the relevant attributes including what must be supported. But that leads to a lot conditions because not always all details can be provided. Another difficulty arises if vendors want to implement a subset from this guide. Then the must-support flag leads to a lot of confusion:

Base MustSupport ProfilemustSupport on category, status, effectiveDate, interpretation, ..conditional mustSupport on valueconditional mustSupport on value.unitconditional mustSupport on componentconditional mustSupport on component.valueconditional mustSupport on component.value.unitBlood PressureBody WeightBody HeightBody Temp..derived fromderived fromderived fromderived fromderived from

That introduces a huge burden on the developer to identify what he needs to do.

How can we create and establish a profile hierarchy to overcome this complex situation? 3 Level Profile Hierarchy!

A possible way out is to create a three-level profile hierarchy that separates requirements depending on the more detailed specialisation for a specific vital sign element:

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.valueobligation SHALL handle exactlymustSupport on component.value.unitobligation SHALL handle equivalentBlood PressureBody WeightBody HeightBody Temp..derived fromderived fromderived fromderived 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.

Using Obligations? Actor-specific profiles!

In the previous section obligations are mentioned with the different classes. It is debatable in which way they should be added or not. This would probably imply different profiles for creators and consumers. But this is another discussion.

Whether we use (and introduce) obligations is another discussion? 4 Level Profile Hierarchy!

The vital signs discussion has revealed that different expectations are leading to different requirements. The most prominent question is: What is a vital sign information?

A hierarchy with at least 4 levels may help to clarify that:

Base MustSupport ProfilemustSupport on category, status, effectiveDate, interpretation, ..Single-Value ProfilemustSupport on valuemustSupport on value.unitMulti-Value ProfilemustSupport on componentmustSupport on component.valuemustSupport on component.value.unitBlood PressureBP SpotBP AverageBP Spot Non-InvasiveBP Spot InvasiveBody WeightBody HeightBody TempBody Temp CoreBody Temp Surface..derived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromderived fromLegend:Artifacts in green seem to be suitable for inclusion in the vital signs guide.The ones in orange require futher refinement.

The coloring scheme may help to interpret.