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

QDM to QI-Core mapping - Encounter

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: High High
    • US QI Core (FHIR)
    • 2.0 [deprecated]
    • Clinical Quality Information
    • QICore Encounter
    • 8.11.3 Encounter, Order, 8.11.4 Encounter, Performed, 8.11.5 Encounter, Recommended
    • Hide

      Change:
      . Section 8.11.3 Encounter, Order .status mapping: Remove “on-hold” — Constrain to one or more of active, completed
      2. Section 8.11.4 Encounter, Performed .status: Keep: constrain to - arrived, triaged, in-progress, on-leave, finished
      Add text: Note: most retrospective eCQMs will constrain Encounter.status to “finished”. Measures designed to monitor active encounters should consider using “in-progress”
      3. Section 8.11.4 Encounter, Performed Attribute row, comment column: PresentOnAdmissionIndicator (code): Keep:
      Indicator of whether the Encounter diagnosis was present at the time of admission
      Add:
      Note: this element uses the value set (required) diagnosis-on-admission (the same value set as used with the claim resource)
      4. Section 8.11.5 Encounter, Recommended .status mapping: Remove “on-hold” — Constrain to one or more of active, completed

      Show
      Change: . Section 8.11.3 Encounter, Order .status mapping: Remove “on-hold” — Constrain to one or more of active, completed 2. Section 8.11.4 Encounter, Performed .status: Keep: constrain to - arrived, triaged, in-progress, on-leave, finished Add text: Note: most retrospective eCQMs will constrain Encounter.status to “finished”. Measures designed to monitor active encounters should consider using “in-progress” 3. Section 8.11.4 Encounter, Performed Attribute row, comment column: PresentOnAdmissionIndicator (code): Keep: Indicator of whether the Encounter diagnosis was present at the time of admission Add: Note: this element uses the value set (required) diagnosis-on-admission (the same value set as used with the claim resource) 4. Section 8.11.5 Encounter, Recommended .status mapping: Remove “on-hold” — Constrain to one or more of active, completed
    • Floyd Eisenberg/Stan Rankin: 17-0-0
    • Correction
    • Non-substantive

    Description

      1. Section 8.11.3 Encounter, Order .status mapping: Remove “on-hold” — Constrain to one or more of active, completed
      2. Section 8.11.4 Encounter, Performed .status: Keep: constrain to - arrived, triaged, in-progress, on-leave, finished
      Add text: Note: most retrospective eCQMs will constrain Encounter.status to “finished”. Measures designed to monitor active encounters should consider using “in-progress”

      3. Section 8.11.4 Encounter, Performed Attribute row, comment column: PresentOnAdmissionIndicator (code): Keep:
      Indicator of whether the Encounter diagnosis was present at the time of admission
      Add:
      Note: this element uses the value set (required) diagnosis-on-admission (the same value set as used with the claim resource)

      4. Section 8.11.5 Encounter, Recommended .status mapping: Remove “on-hold” — Constrain to one or more of active, completed

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            feisenberg Floyd Eisenberg
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: