2015May core #1268 - Suggestions for Event definition via ValueSet Resource

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • FHIR Infrastructure
    • Messaging
    • 2.4.6
    • Hide

      We have dropped the list of messaging event codes. Will also drop the language of "Additional events may be defined elsewhere...." as it no longer applies. This is just vocabulary binding to be defined by local implementations as any other.

      Show
      We have dropped the list of messaging event codes. Will also drop the language of "Additional events may be defined elsewhere...." as it no longer applies. This is just vocabulary binding to be defined by local implementations as any other.
    • Ewout Kramer/Grahame Grieve: 10-0-0
    • Non-substantive
    • DSTU1 [deprecated]

      Existing Wording: Additional events may be defined elsewhere, though this specification does not yet define how. DSTU: Input on this is sought during the trial use period.

      Comment:

      Input on event types: FHIR currently defines an OperationDefinition to define operations, so a MessagingDefinition could also be created. This feels overly constraining though. Why not use a specific ValueSet resource to define system events?

            Assignee:
            Unassigned
            Reporter:
            seanmoore
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: