Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Highest
-
FHIRCast (FHIR)
-
2.0.0
-
Infrastructure & Messaging
-
Event format [deprecated]
-
2.3.2
-
-
Eric Martin / Alex Z Liu: 7-0-0
-
Clarification
-
Non-compatible
Description
Taken together these statements imply that proprietary events only have "focus" components, and no "suffix" (as the event can't be separated at the dash). This leads to the conclusions that (1) * will match all events including propietary events; (2) - will match all non-proprietary events, and (3) that aside from , there is no way to subscribe to a set of proprietary events without enumerating them (something along the lines of foo_ isn't permitted to match foo_blarg and foo_baz). Please update text to clarify whether these conclusions are accurate.
Existing Wording:
The fhir-resource indicates the focus of the event; the suffix defines the type of event. … Proprietary events SHALL NOT contain a dash (“-“). … Wild cards are expressed as a * replacing either the fhir-resource or suffix with * indicates any events that match the resulting definition are requested.
(Comment 4 - imported by: Lloyd McKenzie)
Attachments
Issue Links
- is duplicated by
-
FHIR-37875 we should remove the example of "typical" wildcard usage in events
- Duplicate
- is voted on by
-
BALLOT-37110 Affirmative - Elliot Silver : 2022-May-FHIR IG FHIRCast R1 STU
- Balloted