Skip to content

Commit 69f4823

Browse files
committed
Minor edit
1 parent 0ae5ecd commit 69f4823

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/healthcare-apis/iot/overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,15 +31,15 @@ The following diagram outlines the basic elements of how the MedTech service tra
3131

3232
The MedTech service processes device data in five stages:
3333

34-
1. **Ingest** - The MedTech service asynchronously loads the device messages from the event hub at high speed.
34+
1. **Ingest** - The MedTech service asynchronously reads the device message from the event hub at high speed.
3535

3636
2. **Normalize** - After the device message has been ingested, the MedTech service uses the device mapping to streamline and convert the device data into a normalized schema format.
3737

3838
3. **Group** - The normalized data is then grouped by parameters to prepare it for the next stage of processing. The parameters are: device identity, measurement type, time period, and (optionally) correlation ID.
3939

4040
4. **Transform** - When the normalized data is grouped, it's transformed through the FHIR destination mapping and is ready to become FHIR Observations.
4141

42-
5. **Persist** - After the transformation is done, the new data is sent to the FHIR service and persisted as FHIR Observations.
42+
5. **Persist** - After the transformation is done, the newly transformed data is sent to the FHIR service and persisted as FHIR Observations.
4343

4444
## Key features of the MedTech service
4545

0 commit comments

Comments
 (0)