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

All request resources should support the fields from the request pattern

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • Appointment
      AppointmentResponse
      CarePlan
      Claim
      CommunicationRequest
      Contract
      CoverageEligibilityRequest
      DeviceRequest (was DeviceUseRequest)
      EnrollmentRequest
      ImmunizationRecommendation
      MedicationRequest
      NutritionOrder (was NutritionRequest)
      RequestOrchestration (was RequestGroup)
      ServiceRequest (Diagnostic/Procedure/ReferralRequest)
      SupplyRequest
      Task
      Transport
      VisionPrescription
      Request Pattern
    • Hide

      Will update the tooling to:

      a) flag places where mappings do not exist to pattern elements

      b) create warnings where elements are unmapped, or are mapped with differences but no explanation has been provided

      c) ensure provided explanations render as part of the flyovers in the pattern summary tables

      d) will raise tracker items with all WGs for them to review the report and fix things

      In the event the tooling is not complete prior to WGM, will manually review and raise tracker items on the key elements Bas listed.

      Show
      Will update the tooling to: a) flag places where mappings do not exist to pattern elements b) create warnings where elements are unmapped, or are mapped with differences but no explanation has been provided c) ensure provided explanations render as part of the flyovers in the pattern summary tables d) will raise tracker items with all WGs for them to review the report and fix things In the event the tooling is not complete prior to WGM, will manually review and raise tracker items on the key elements Bas listed.
    • Bas van den Heuvel/Jose Costa Teixeira: 5-0-0
    • Enhancement
    • Non-substantive
    • R5

    Description

      Many of the request resources do have fields that correspond the fields indicated in the request pattern and they should.

      All fields should be considered.
      The fields basedOn, groupIdentifier, intent, requester and subject are critical because main design/interaction patterns in FHIR depend on them.
      The field category is very usefull but not present on any of them.

      This should be fixed in R5.

      Attachments

        Activity

          People

            lloyd Lloyd McKenzie
            bvdh Bas van den Heuvel
            Bas van den Heuvel
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: