Blood Pressure Cross-Country Cross-Language Cross-Paradigm (Demo) IG
0.6.3 - ci-build

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

ITS (Profiling)

The implementation technology (ITS) is responsible for how the data/information has to be represented by using the different containers being available. As a consequence, the way highly varies.

FHIR

FHIR provides a set of containers called resources that can be arranged in form class diagrams. In order to get that represented in a way allowing for assigning all details a UML package represents a resource, and the classes inside that package are responsible for showing the internal structures:

Representation in FHIR: ITSRepresentation in FHIR: ITSPatient ResourceObservation Resource: BPObservation Resource: ExertionObservation Resource: Body WeightMedicationStatementMedicationPractitionerRole ResourcePractitioner ResourceResource DevicePatientidentifiernamegenderdobMainObservationDataidentifierstatuscategorycodeeffectiveDateTimenotebodySitemethodComponent: systoliccodevaluedataAbsentReasoninterpretationreferenceRangeComponent: diastoliccodevaluedataAbsentReasoninterpretationreferenceRangeMainObservationDataidentifierstatuscategorycodevalueinterpretationeffectiveDateTimenoteMainObservationDataidentifierstatuscategorycodevalueinterpretationeffectiveDateTimenoteMedicationStatementidentifierstatuscategoryeffectiveDateTimeMedicationidentifiercodestatusdoseFormIngredientitemisActivestrengthPractitionerRoleidentifieractivecodeperiodPractitioneridentifiernameDeviceidentifierdisplayNamestatusname[]modelNumberserialNumbercategorytype0..10..1ingredientsubject0..1performer (self)0..*performer (professional)0..*subject0..1subject0..1medicationsubject10..1

Resources:

open details:

  • medication

v2.x/v2+

v2x/v2+ is a line oriented and delimitered format that could be best represented in form of tables showing the fields for each line/row. The leftmost table operates as the whole message structure:

"Representation in v2x: ITS""Representation in v2x: ITS"segmentv2 message1MSH2..3   4   5   6   7   8   9more OBX segmentsfieldPID-segment3identifier5name7date of birth8genderfieldOBX-segment1seq no (=1)2value type3code for blood pressure8interpretation code14date/time of observationfieldPRT-segment_involved physicianfieldOBX (systolic) segment1seq no (=2)2value type (= NM)3code for systolic blood pressure value5value6unit7reference range8interpretation codefieldOBX (diastolic) segment1seq no (=3)2value type (NM)3code for distolic blood pressure value5value6unit7reference range8interpretation codefieldOBX (exertion) segment1seq no (=4)2value type (NM)3code for exertion5value6unit7reference range8interpretation code

Segments:

open details:

  • medication
  • device

Model in Version 3.0

tbd: the drawing is just the first draft!!!!

The drawing collects all details and arranges them as a domain message information model (D-MIM):

Representation in V3: ITS (Draft!)Representation in V3: ITS (Draft!)PatientclassCode = PSNdeterminerCode = INSTidnamegenderbirthTimeObservation: Blood PressureidstatuscategorycodeeffectiveDateTimenotebodySitemethodEntry PointObservation: systoliccodevaluedataAbsentReasoninterpretationreferenceRangeObservation: diastoliccodevaluedataAbsentReasoninterpretationreferenceRangehasComponenttypeCode = COMPhasComponenttypeCod = COMPObservation: ExertionclassCodeidstatuscategorycodevalueinterpretationeffectiveDateTimenoteObservation: Body WeightclassCodeidstatuscategorycodevalueinterpretationeffectiveDateTimenoteSubstanceAdministrationidstatuscategoryeffectiveDateTimeParticipationtypeCode = PATParticipationtypeCodeParticipationtypeCodeParticipationtypeCode = SUBJParticipationtypeCode = SUBSTParticipationtypeCode = SUBJParticipationtypeCode = SUBJPatientRoleclassCode = PATPerformerRoletypeCode = PERFidstatus = activecodeperiodDeviceRolePatientRoleclassCode = PATSubstanceRoleclassCode = PATPatientRoleclassCode = PATPatientRoleclassCode = PATPractitionerclassCode = PRACTidnameMaterialclassCode = MATdeterminerCode = INSTidcodeDeviceidentifierdisplayNamestatusname[]modelNumberserialNumbercategorytype0..10..1subject0..1subject0..1subject0..1performperformer (self)0..*0..110..1subject0..1

CDA

tbd: the drawing is just the first draft!!!!

The following drawing shows the surroundings from a document perspective. The D-MIM has to be included replacing the

Representation in CDA: ITS (Draft!)Representation in CDA: ITS (Draft!)Clinical DocumentclassCode = DOCCLINmoodCode = EVNidstatuscategorycodeeffectiveDateTimenotebodySitemethodhasComponenttypeCode = COMPParticipationtypeCode = RCTPatientRoleclassCode = PATPatientclassCode = PSNdeterminerCode = INSTidnamegenderbirthTimeStructured BodyclassCode = DOCBODYmoodCode = EVNidstatuscategorycodeeffectiveDateTimenotebodySitemethodSectionclassCode = DOCSECTmoodCode = EVNcodetitletexthasComponenttypeCode = COMPhasComponenttypeCode = COMPObservation (for BP D-MIM)classCode = OBSmoodCode = EVNidstatuscategorycodeeffectiveDateTimenotebodySitemethodEntry PointExit Pointto includeV3 model10..111..*1..*

Binding to terminologies

The terminology needed should be identical for each ITS because an ITS does not make any assumption about codes. It should be sufficien to hook them in.