Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-37074

The key should use resource type.

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIRCast (FHIR)
    • 2.1.0-ballot [deprecated]
    • Infrastructure & Messaging
    • STU
    • DiagnosticReport Events
      Event format [deprecated]
      ImagingStudy Events
    • Hide
       The specification is indeed saying both things: event-names of context-change events are required to be lowercase. The generic guidance states that the event-names are case-insensitive.
       
      We will update the the specification to state:
       * event-names are case-INsensitive, in the specification we will use Upper-Camel case
       * keys in context will be case-sensitive and lower case.
       * scopes will use the same definition as event-names (case insensitive)
       * update all examples and names to use UpperCamel-case event names.
       * state that Hubs and Subscribers SHALL be case insensitive for event-names (relates to context-change requests and subscribing).
      Show
       The specification is indeed saying both things: event-names of context-change events are required to be lowercase. The generic guidance states that the event-names are case-insensitive.   We will update the the specification to state:  * event-names are case-INsensitive , in the specification we will use Upper-Camel case  * keys in context will be case-sensitive and lower case.  * scopes will use the same definition as event-names (case insensitive)  * update all examples and names to use UpperCamel-case event names.  * state that Hubs and Subscribers SHALL be case insensitive for event-names (relates to context-change requests and subscribing).
    • Eric Martin / Bas van den Heuvel: 6-0-0
    • Clarification
    • Non-substantive

      The key used for indicating a context change event's FHIR resource SHALL be the lower-case resourceType of the resource. In the case the resource refers to other FHIR resources that represent their own context, these can be included as well. The resources to include are defined in the corresponding event definition in the [event catalog](3_Events.html).

      The diagnosticreport and imagingstudy events deviate from this. These should follow this guideline.

      Why is the name case-sensitive? Other parts of the spec say differently.

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: