Skip to content

Commit 21ce4b2

Browse files
committed
Updates based on feedback
1 parent 43dd91d commit 21ce4b2

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

articles/healthcare-apis/events/events-faqs.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: fhir
88
ms.topic: reference
9-
ms.date: 03/28/2022
9+
ms.date: 04/04/2022
1010
ms.author: jasteppe
1111
---
1212

@@ -35,11 +35,16 @@ For more information about the FHIR service delete types, see [FHIR REST API cap
3535

3636
### Does Events support FHIR bundles?
3737

38-
Yes. Events support [FHIR bundles](https://www.hl7.org/fhir/bundle.html) in the following ways:
38+
Yes. The Events feature is designed to emit notifications of data changes at the FHIR resource level.
3939

40-
* **Batch**: An event is emitted for each successful bundle operation, however, if one of the operations generates an error, no event is emitted for that operation. For example: the batch bundle contains five operations, however, there's an error with one of the operations. Events are emitted for the four successful operations with no event emitted for the operation that generated an error.
40+
Events support FHIR bundles in the following ways:
4141

42-
* **Transaction**: An event is emitted for each successful bundle operation as long as there are no errors. If there's a single error within a transaction bundle, then no events are emitted. For example: the transaction bundle contains five operations, however, there's an error with one of the operations. No events are emitted for that bundle.
42+
- **Batch**: An event is emitted for each successful data change operation in a bundle. If one of the operations generates an error, no event is emitted for that operation. For example: the batch bundle contains five operations, however, there's an error with one of the operations. Events are emitted for the four successful operations with no event emitted for the operation that generated an error.
43+
44+
- **Transaction**: An event is emitted for each successful bundle operation as long as there are no errors. If there's any errors within a transaction bundle, then no events are emitted. For example: the transaction bundle contains five operations, however, there's an error with one of the operations. No events are emitted for that bundle.
45+
46+
> [!NOTE]
47+
> Events are not sent in the sequence of the data operations in the FHIR bundle.
4348
4449
### What DICOM image events does Events support?
4550

0 commit comments

Comments
 (0)