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.1 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
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: ITS Representation in FHIR: ITS Patient Resource Observation Resource: BP Observation Resource: Exertion Observation Resource: Body Weight MedicationStatement Medication PractitionerRole Resource Practitioner Resource Resource Device Patient identifier name gender dob MainObservationData identifier status category code effectiveDateTime note bodySite method Component: systolic code value dataAbsentReason interpretation referenceRange Component: diastolic code value dataAbsentReason interpretation referenceRange MainObservationData identifier status category code value interpretation effectiveDateTime note MainObservationData identifier status category code value interpretation effectiveDateTime note MedicationStatement identifier status category effectiveDateTime Medication identifier code status doseForm Ingredient item isActive strength PractitionerRole identifier active code period Practitioner identifier name Device identifier displayName status name[] modelNumber serialNumber category type 0..1 0..1 ingredient subject 0..1 performer (self) 0..* performer (professional) 0..* subject 0..1 subject 0..1 medication subject 1 0..1
Resources:
open details:
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:
"Representation in v2x: ITS" "Representation in v2x: ITS" segment v2 message 1 2 3 4 5 6 field PID 3 identifier 5 name 7 date of birth 8 gender field OBX 1 seq no (=1) 2 value type 3 code for blood pressure 8 interpretation code 14 date/time of observation field PRT _ involved physician field OBX (systolic) 1 seq no (=2) 2 value type (= NM) 3 code for systolic blood pressure value 5 value 6 unit 7 reference range 8 interpretation code field OBX (diastolic) 1 seq no (=3) 2 value type (NM) 3 code for distolic blood pressure value 5 value 6 unit 7 reference range 8 interpretation code field OBX (exertion) 1 seq no (=4) 2 value type (NM) 3 code for exertion 5 value 6 unit
Segments:
open details:
CDA
tbd: the drawing is just the first draft!!!!
Representation in CDA: ITS (Draft!) Representation in CDA: ITS (Draft!) Patient classCode = PSN determinerCode = INST id name gender birthTime Observation: Blood Pressure id status category code effectiveDateTime note bodySite method Observation: systolic code value dataAbsentReason interpretation referenceRange Observation: diastolic code value dataAbsentReason interpretation referenceRange hasComponent typeCode = COMP hasComponent typeCod = COMP Observation: Exertion classCode id status category code value interpretation effectiveDateTime note Observation: Body Weight classCode id status category code value interpretation effectiveDateTime note SubstanceAdministration id status category effectiveDateTime Participation typeCode = PAT Participation typeCode Participation typeCode Participation typeCode = SUBJ Participation typeCode = SUBST Participation typeCode = SUBJ Participation typeCode = SUBJ PatientRole classCode = PAT PerformerRole typeCode = PERF id status = active code period DeviceRole PatientRole classCode = PAT SubstanceRole classCode = PAT PatientRole classCode = PAT PatientRole classCode = PAT Practitioner classCode = PRACT id name Material classCode = MAT determinerCode = INST id code Device identifier displayName status name[] modelNumber serialNumber category type 0..1 0..1 subject 0..1 subject 0..1 subject 0..1 perform performer (self) 0..* 0..1 1 0..1 subject 0..1
Binding to terminologies
The terminology needed should be identical for each ITS because an ITS does not make any assumption about codes.
