Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
DiagnosticsReport update event [deprecated]
-
3.6.3.1
-
-
Eric Martin / Catie Ladd: 4-0-0
-
Clarification
-
Non-substantive
-
Yes
Description
I suspect ordering of event processing, updates to versionId, etc. is more general than just this event, and the requirement should be moved into a more generic section. At the very least, half of this section is written to cover a generic [FHIR-Resource]-update event, and half to cover the more specific DiagnosticReport-update. Move generic content to a generic section, leave specific content here; or make all content specific.
Existing Wording:
Each DiagnosticReport-update event posted to the Hub SHALL be processed atomically by the Hub (i.e., all entries in the request’s Bundle should be processed prior to the Hub accepting another request).
(Comment 37 - imported by: Lloyd McKenzie)
Attachments
Issue Links
- is voted on by
-
BALLOT-37143 Affirmative - Elliot Silver : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted