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

Event pattern resource should implement the fields from the pattern.

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • FHIR Infrastructure
    • STU
    • AdverseEvent
      AuditEvent
      ChargeItem
      ClaimResponse
      ClinicalImpression
      Communication
      Composition
      Consent
      Contract
      Coverage
      CoverageEligibilityResponse
      DetectedIssue
      DeviceUsage (DeviceUseStatement)
      DiagnosticReport
      DocumentManifest (See List) [deprecated]
      DocumentReference
      Encounter
      EnrollmentResponse
      EpisodeOfCare
      ExplanationOfBenefit
      FamilyMemberHistory
      GenomicStudy
      GuidanceResponse
      ImagingSelection
      ImagingStudy
      Immunization
      ImmunizationEvaluation
      Invoice
      MedicationAdministration
      MedicationDispense
      MedicationStatement
      Observation
      PaymentNotice
      PaymentReconciliation
      Procedure
      Provenance
      QuestionnaireResponse
      RiskAssessment
      SupplyDelivery (was Supply)
      Task
      Transport
      Event 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

      The event resources do not implement the fields from the event pattern. Not implementing these hampers the generic use patterns of the requires in the request-event workflow. This should be avoided.

      All fields are usefull for most resources.
      The specific fields that need to be supported by all event resources because common patterns in FHIR depend on them include: basedOn, category, encounter, subject, occurrence/recorded.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: