Skip to content

Commit 1f96620

Browse files
msjasteppenamalu
andauthored
Applying feedback.
Co-authored-by: namalu <[email protected]>
1 parent 36d2e9e commit 1f96620

File tree

1 file changed

+12
-4
lines changed

1 file changed

+12
-4
lines changed

articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,15 @@ The MedTech service requires two types of [JSON](https://www.json.org/) mappings
2323
2424
## FHIR destination mapping basics
2525

26-
Once the device content is extracted into a normalized model, the data is collected and grouped according to device identifier, measurement type, and time period. The output of this grouping is sent for conversion into a [FHIR Observation](https://www.hl7.org/fhir/observation.html). The FHIR destination mapping controls how the data extracted from a device message is mapped into a FHIR observation. Should an observation be created for a point in time or over a period of an hour? What codes should be added to the observation? Should the value be represented as [SampledData](https://www.hl7.org/fhir/datatypes.html#SampledData) or a [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity)? These data types are all options the FHIR destination mapping configuration controls.
26+
The FHIR destination mapping controls how the data extracted from a device message is mapped into a FHIR observation.
27+
28+
- Should an observation be created for a point in time or over a period of an hour?
29+
- What codes should be added to the observation?
30+
- Should the value be represented as [SampledData](https://www.hl7.org/fhir/datatypes.html#SampledData) or a [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity)?
31+
32+
These data types are all options the FHIR destination mapping configuration controls.
33+
34+
Once a device message is transformed into a normalized data model, the data is collected for transformation to a [FHIR Observation](https://www.hl7.org/fhir/observation.html). If the Observation type is [SampledData](https://www.hl7.org/fhir/datatypes.html#SampledData), the data is grouped according to device identifier, measurement type, and time period (time period can be either 1 hour or 24 hours). The output of this grouping is sent for conversion into a single [FHIR Observation](https://www.hl7.org/fhir/observation.html) that represents the time period for that data type. For other Observation types ([Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity), [CodeableConcept](https://www.hl7.org/fhir/datatypes.html#CodeableConcept) and [string](https://www.hl7.org/fhir/datatypes.html#string)) data is no grouped, but instead each measurement is transformed into a single Observation representing a point in time.
2735

2836
> [!TIP]
2937
> For more information about how the MedTech service processes device message data into FHIR Observations for persistence on the FHIR service, see [Overview of the MedTech service device message processing stages](overview-of-device-message-processing-stages.md).
@@ -90,7 +98,7 @@ Represents the [SampledData](http://hl7.org/fhir/datatypes.html#SampledData) FHI
9098

9199
### Quantity
92100

93-
Represents the [Quantity](http://hl7.org/fhir/datatypes.html#Quantity) FHIR data type. If more than one value is present in the grouping, only the first value is used. When new value arrives that maps to the same observation it overwrites the old value.
101+
Represents the [Quantity](http://hl7.org/fhir/datatypes.html#Quantity) FHIR data type. This type will create a single, point in time, Observation. If new value arrives that contains the same device identifier, measurement type, and time period, the previous Observation will be updated to the new value.
94102

95103
| Property | Description
96104
| --- | ---
@@ -100,7 +108,7 @@ Represents the [Quantity](http://hl7.org/fhir/datatypes.html#Quantity) FHIR data
100108

101109
### CodeableConcept
102110

103-
Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConcept) FHIR data type. The actual value isn't used.
111+
Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConcept) FHIR data type. The value in in the normalized data model is not used, and instead when this type of data is received, an Observation will be created with a specific code representing that an observation was recorded at a specific point in time.
104112

105113
| Property | Description
106114
| --- | ---
@@ -112,7 +120,7 @@ Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConc
112120

113121
### String
114122

115-
Represents the [string](https://www.hl7.org/fhir/datatypes.html#string) FHIR data type. If more than one value is present in the grouping, only the first value is used. If new value arrives that maps to the same observation, it overwrites the old value.
123+
Represents the [string](https://www.hl7.org/fhir/datatypes.html#string) FHIR data type. This type will create a single, point in time, Observation. If new value arrives that contains the same device identifier, measurement type, and time period, the previous Observation will be updated to the new value.
116124

117125
### Example
118126

0 commit comments

Comments
 (0)