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

Wow! That's a lot of events, given that almost no one supports FHIR Subscriptions R5.

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive with Modification
    • Specification:
      US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Public Health
    • Related Page(s):
      Artifacts Summary
    • Related Section(s):
      15.33.1
    • Grouping:
    • Resolution Description:
      Hide

      After careful consideration and discussion for multiple public health use cases, we will retain the value set with all the values currently listed. The value set represents the core set of all the events that could be used for subscriptions and notifications. Not all the events need to be implemented by the EHRs immediately. This core set would also be harmonized with other IGs and potentially across WGs as the set of events that commonly occur in clinical care and could be used for subscriptions and notifications.

      The CONTENT IGs for different use cases will identify the subset of the events required for the use case. The EHR vendors can support the specific events based on the use cases and content IGs that they choose to implement.

      Show
      After careful consideration and discussion for multiple public health use cases, we will retain the value set with all the values currently listed. The value set represents the core set of all the events that could be used for subscriptions and notifications. Not all the events need to be implemented by the EHRs immediately. This core set would also be harmonized with other IGs and potentially across WGs as the set of events that commonly occur in clinical care and could be used for subscriptions and notifications. The CONTENT IGs for different use cases will identify the subset of the events required for the use case. The EHR vendors can support the specific events based on the use cases and content IGs that they choose to implement.
    • Change Category:
      Clarification

      Description

      There's a lot of named events in your valueset, which you're requiring the EHR to support. It's really hard to standardize a clinical event definition exactly. In addition to defining these topics/events more formally, you should consider better prioritizing them and starting with fewer being required.

      (Comment 22 - imported by: Jean Duteau)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Isaac.Vetter Isaac Vetter
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: