Skip to content

Commit 5a5bed5

Browse files
committed
Minor update
1 parent 61625d4 commit 5a5bed5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/healthcare-apis/iot/understand-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The MedTech service device message data processing follows these steps and in th
2222
> [!div class="checklist"]
2323
> - Ingest
2424
> - Normalize - Device mappings applied.
25-
> - Group - Optional.
25+
> - Group - (Optional)
2626
> - Transform - FHIR destination mappings applied.
2727
> - Persist
2828
@@ -52,7 +52,7 @@ Normalize is the next stage where device message data is processed using user-se
5252

5353
The normalization process not only simplifies data processing at later stages, but also provides the capability to project one device message into multiple normalized messages. For instance, a device could send multiple vital signs for body temperature, pulse rate, blood pressure, and respiration rate in a single device message. This device message would create four separate FHIR Observation resources. Each resource would represent a different vital sign, with the device message projected into four different normalized messages.
5454

55-
## Group - Optional
55+
## Group - (Optional)
5656
Group is the next *optional* stage where the normalized messages available from the MedTech service normalization stage are grouped using three different parameters:
5757

5858
> [!div class="checklist"]

0 commit comments

Comments
 (0)