encounter dx on admit needed?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • (many)
    • Da Vinci Notifications Patient Admit/Discharge Use Case
    • Hide

      it is our mutual experience that a diagnosis or a provisional diagnosis is available long before discharge - including a diagnosis on an admit/discharge notification allows the recipient to determine if additional action is required.

      add clarifying text

      Show
      it is our mutual experience that a diagnosis or a provisional diagnosis is available long before discharge - including a diagnosis on an admit/discharge notification allows the recipient to determine if additional action is required. add clarifying text
    • Riki Merrick / Craig Newman: 3-0-1
    • Clarification
    • Non-substantive

      The stated purpose of this is for "sending unsolicited notifications to the appropriate actors when triggered by an event or request". The example use case is for admission and discharge. On the html web page listed (or here http://hl7.org/fhir/us/davinci-alerts/2020FEB/usecases.html) Figure 5 shows the encounter diagnosis. It isn't required but including it seems very odd. Typically an encounter diagnosis is not available until well after discharge. If the purpose is to give an immediate notification when a patient is discharged, then why would you even list this element. It puts pressure on implementers to try to provide it or at least to look into it. Why not just leave it off and allow systems to query for it later?

            Assignee:
            Unassigned
            Reporter:
            rberge
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: