Several request-related extensions are defined on NutritionOrder only

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Request Pattern
    • Hide

      Most places where the extensions weren't defined were either because there was a 'core' element on the Request resource or because the concept didn't make sense for the concept (e.g. "doNotPerform" on an Appointment).  However, we did find some where we believe the scope of the extension should be extended to include other resources.  Specifically:

      DeviceRequest - add doNotPerform, performerOrder

      Task - add doNotPerform, replaces, add performerOrder (also change to CodeableReference)

      SupplyRequest - add replaces, performerOrder

       

      Appointment - add insurance, replaces

       

      CarePlan - add insurance, relevantHistory?, performerOrder

      CommunicationRequest - add insurance?

       

      Will create change requests for the relevant work groups to consider adding these concepts - either as core or by extending the scope of the existing extensions to include their resources.

      Show
      Most places where the extensions weren't defined were either because there was a 'core' element on the Request resource or because the concept didn't make sense for the concept (e.g. "doNotPerform" on an Appointment).  However, we did find some where we believe the scope of the extension should be extended to include other resources.  Specifically: DeviceRequest - add doNotPerform, performerOrder Task - add doNotPerform, replaces, add performerOrder (also change to CodeableReference) SupplyRequest - add replaces, performerOrder   Appointment - add insurance, replaces   CarePlan - add insurance, relevantHistory?, performerOrder CommunicationRequest - add insurance?   Will create change requests for the relevant work groups to consider adding these concepts - either as core or by extending the scope of the existing extensions to include their resources.
    • Jose Costa Teixeira/John Hatem: 4-0-0
    • Correction
    • Non-substantive

      All of the extensions listed on the Request Pattern HL7 Extensions page are specified to apply only to NutritionOrder (except for request-statusReason, which applies broadly).

      But since these are all general request extensions, they should be useable more broadly than just NutritionOrder.

       

            Assignee:
            Lloyd McKenzie
            Reporter:
            Bryn Rhodes
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: