Skip to content

Commit e17967b

Browse files
committed
More updates
1 parent edf59ea commit e17967b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/healthcare-apis/iot/frequently-asked-questions.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ The MedTech service supports the [HL7 FHIR® R4](https://www.hl7.org/impleme
3333

3434
### Why do I have to provide device and FHIR destination mappings to the MedTech service?
3535

36-
The MedTech service requires device and FHIR destination mappings to perform normalization and transformation processes on device message data. To learn how the MedTech service transforms device message data into Observation resources, see [Understand the MedTech service device message data transformation](understand-service.md).
36+
The MedTech service requires device and FHIR destination mappings to perform normalization and transformation processes on device message data. To learn how the MedTech service transforms device message data into [FHIR Observations](https://www.hl7.org/fhir/observation.html), see [Understand the MedTech service device message processing stages](understand-service.md).
3737

3838
### How long does it take for device message data to show up in the FHIR service?
3939

40-
The MedTech service buffers Observation resources created during the transformation stage and provides near real-time processing. However, this buffer can potentially delay the persistence of Observation resources to the FHIR service up to five minutes. To learn how the MedTech service transforms device message data into Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).
40+
The MedTech service buffers [FHIR Observations](https://www.hl7.org/fhir/observation.html) created during the transformation stage and provides near real-time processing. However, this buffer can potentially delay the persistence of FHIR Observations to the FHIR service up to ~five minutes. To learn how the MedTech service transforms device message data into FHIR Observations, see [Understand the MedTech service device message processing stages](understand-service.md).
4141

42-
### Why are the device messages added to the event hub not showing up as Observation resources in the FHIR service?
42+
### Why are the device messages added to the event hub not showing up as FHIR Observations in the FHIR service?
4343

4444
> [!TIP]
4545
> Having access to MedTech service logs is essential for troubleshooting and assessing the overall health and performance of your MedTech service.

0 commit comments

Comments
 (0)