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

When to add a pattern to HRex

    XMLWordPrintableJSON

Details

    • Icon: Question Question
    • Resolution: Considered - Question answered
    • Icon: Medium Medium
    • US Da Vinci HRex (FHIR)
    • current
    • Clinical Interoperability Council
    • (NA)
    • Hide

      In general, we don't put content into HRex unless it's done (more or less consistently) in at least two Da Vinci IGs. It's possible we could put something in HRex that was only used in one place if there was a near certainty of it being used elsewhere soon.

      Show
      In general, we don't put content into HRex unless it's done (more or less consistently) in at least two Da Vinci IGs. It's possible we could put something in HRex that was only used in one place if there was a near certainty of it being used elsewhere soon.

    Description

      See FHIR-26212:

       

       We deferred this question and responded at the time:

      IN this IG we are specifying a simple more FHIR RESTful operation based approach see FHIR-26098.

      This constrained form of messaging is currently supported only by this IG. Agree that after publication and general vetting of the approach the exchange pattern content should should be merged into the Da Vinci hrex IG and referenced from it in a future version of this IG."When should this pattern be considered for hrex.

       

      We are not aware of any other DV guides that treat notifications using FHIR messaging like the Notifications guide and don't think it is appropriate at this time to generalize this solution.  But we should have some guidelines when it would be appropriate to move  into HRex, and generally when to use HRex vs a "one-solution"?

      Attachments

        Activity

          People

            Unassigned Unassigned
            ehaas Eric Haas
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: