Body Weight Cross-Country Cross-Language Cross-Paradigm (Demo) IG
0.1.1 - ci-build

Body Weight 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.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/bodyweight/ and changes regularly. See the Directory of published versions

Body Weight

Official URL: http://bodyweight.oemig.de/fhir/ImplementationGuide/bodyweight Version: 0.1.1
Draft as of 2024-12-08 Computable Name: BodyWeight

This is the new homepage for body weight. It has been separated from the vital signs demo guide to demonstrate further how individual guides should be written. It still requires the addition of more details.

Step 1: MindMap

The following mindmap collects and sorts all aspects around body weight that are necessary for a correct interpretation and clinical use. It has to be recognized that some artifacts (eg. reference range) are abbreviated, and the corresponding details must be duplicated. Unfortunately, PlantUML mindmaps do not allow for cross-links to denote that.

The following diagram aggregates all aspects that can be found somewhere. It tries to arrange them in a way that helps to understand the semantics, and to sort them. For the moment, additional explanatory text has not been duplicated from other sources for copyright and IP reasons. It can be expected, that this will be done later on.

Body WeightadministrativeidentifierdateTimeDT: instantencounterinvolved personssubjectauthorperformerprotocolmeasuring typeDT: codemeasuredestimatedclothingDT: codenonelightmiddleheavyeatingDT: codebeforeMealafterMealshoesDT: booleancommentDT: textmeasurementvalueDT: integerunitkgg (for newborns)reference rangelowhighageinterpretationDT: codelownormalhighlost body structures

Step 2: Information Model

Body Weight Information ModelBody Weightidentifier: identifiervalue: decimalinterpretation: codemeasuringType: codeclothing: codeeating: codeshoes: booleandateTime: instantcomment: stringBody Partspart: codeSubjectAuthorPerformerReference Rangelowhighage10..10..10..1lost0..*

Step 3: Hierarchy for Vital Signs Profiles (informative)

Body Weight HierarchyVital Signstatus: codecategory: code = vital-signcode: codeobservationDate: instant|periodBody Weightcategory: code = vital-sign-bwcode: codevalue: integerunit: codeinterpretation: codedate: instant...PatientAuthorUS Core BWDE Core BWDE KBV BWDE MII BWDE Standard BW for EHRsubjectauthor

Step 4: Technology Binding (ITS)

How to represent the same information in different standards?

Step 4a: Profile (with FHIR)

Body Weight FHIR ProfileBody Weight (Observation)category: vital-sign-bwcode: codevalue: integerunit: codedataAbsentReasonreferenceRange: Rangeinterpretation: codemethod: codedateTime: instantLost Body Partscode: codeClothingcodeShoescodeEatingcodeAuthorSubjectidagePerformer0..110..10..*0..10..10..1

Step 4b: Template (with CDA)

tbd

Step 4c: OBX Segment Group profile (with v2.x)

Please see logical model.

As a draft:

Segment Card. Content Value Type Unit Code Comment
PID 1..1 Patient information n/a n/a n/a PID-3
PV1 1..1 Visit information n/a n/a n/a PV1-19
OBX 1..1 body weight NM (k)g $LOINC#tbd main entry into BW results
PRT 0..* for different participants n/a n/a n/a appropriate participant definitions are necessary
OBX 0..1 eating CWE tbd $LOINC#tbd  
OBX 0..1 clothing CWE tbd $LOINC#tbd  
OBX 0..* missing body structures CWE tbd $SCT#tbd  

Notes:

  • It has to be considered that segments are relevant that are not directly represented in the same group.
  • Some codes are just place holders.

Country-specific Derivations

.. are not necessary so far.

References + Specifics

  • US Core
  • DE Core
  • NHS Core