Skip to content

Commit ac276ed

Browse files
committed
Small edits.
1 parent a77a3a8 commit ac276ed

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/event-grid/event-schema-azure-health-data-services.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This article provides the properties and schema for Azure Health Data Services e
1313

1414
### List of Events for Azure Health Data Services REST APIs
1515

16-
These events are triggered when a Fast Healthcare Interoperability Resources (FHIR®) resource is created, updated, or deleted by calling the FHIR service REST APIs.
16+
These events are triggered when a Fast Healthcare Interoperability Resources (FHIR®) Observation is created, updated, or deleted by calling the FHIR service REST APIs.
1717

1818
|Event name|Description|
1919
|----------|-----------|
@@ -29,7 +29,7 @@ These Events are triggered when a DICOM image is created or deleted by calling t
2929
|**DicomImageDeleted** |The event emitted after a DICOM image is deleted successfully.|
3030

3131
## Example events
32-
This section contains examples of what Azure Health Data Services Events message data would look like for each FHIR resource and DICOM image event.
32+
This section contains examples of what Azure Health Data Services Events message data would look like for each FHIR Observation and DICOM image event.
3333

3434
> [!NOTE]
3535
> Events data looks similar to these examples with the `metadataVersion` property set to a value of `1`.

articles/healthcare-apis/iot/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
### YamlMime:Landing
22

33
title: MedTech service documentation
4-
summary: MedTech service documentation for the Azure Health Data Services. The MedTech service is a service of the Azure Health Data Services designed to ingest device message data from multiple devices, transform the data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
4+
summary: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
55

66
metadata:
77
title: Azure Health Data Services MedTech service
8-
description: MedTech service documentation for the Azure Health Data Services. The MedTech service is a service of the Azure Health Data Services designed to ingest device message data from multiple devices, transform the data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
8+
description: MedTech service documentation for Azure Health Data Services. The MedTech service is one of the Azure Health Data Services designed to ingest device message data from multiple devices, transform that data into FHIR Observations, which are then persisted in the Azure Health Data Services FHIR service.
99
services: healthcare-apis
1010
ms.service: healthcare-apis
1111
ms.subservice: data-transformation

0 commit comments

Comments
 (0)