Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Da Vinci Unsolicited Notifications Implementation Guide - THIS IS THE LINK TO THE CI BUILD WITH APPLIED TRACKERS


Artifacts of focus

Base Da Vinci Notification Profiles

  • Da Vinci Notifications MessageHeader Profile
  • Da Vinci Notifications Bundle Profile

Da Vinci Admission/Discharge Notification Profiles

  • Da Vinci Admit Notification MessageHeader Profile
  • Da Vinci Discharge Notification MessageHeader Profile
  • Da Vinci Transfer Notification MessageHeader Profile
  • Da Vinci Admit/Transfer/Discharge Notification Condition Profile
  • Da Vinci Admit/Transfer/Discharge Notification Coverage Profile
  • Da Vinci Admit/Transfer/Discharge Notification Encounter Profile


Clinical input requested (if any)

...

Expected participants


Reference Implementations

...

Login to HSPCs Logica Sandbox at: sandbox.hspsconsortium.org/DaVinciALERTS/apps 

quick video demo

Zulip stream

...


Da Vinci Notification Sender Simulation: (Client Facade to simulate Sender) at: http://ehaas.pythonanywhere.com/

Zulip stream

https://chat.fhir.org/#narrow/stream/179207-connectathon-mgmt/topic/DaVinci.20Notifications.20track.20participants

NEED TO CHECK IF WE CAN USE THIS ONE FROM May connectathon - else need to create one


Track Orientation

The recording of Track Orientation session given on April 15, 2020    - DECIDE ON THE UPDATED WEBINAR AND UPDATEAugust 19, 2020:


Track details

System Roles

...

  • Sender - the system responsible for sending the notification, typically operated by the facility or organization where the event occurred
  • Recipient – the system responsible for receiving generated notifications from Notification Senders
  • Intermediary (e.g. ClearingHouse or HIE/HIN)– a system that can act as a central point to receive notifications from multiple Notification Senders and distribute/forward notifications to Notification Recipients based on previously defined subscription policies


They correspond to these roles in the notification transactions:

ActorRole

server-mode

client-mode

Sender

Da Vinci Notification Query Responder

Da Vinci Notification Sender

Intermediary

Da Vinci Notification Receiver,Da Vinci Notification Query Responder

Da Vinci Notification QueryRequester, Da Vinci Notification SenderForwarder

Recipient

Da Vinci Notification Receiver

Da Vinci Notification Query Requester

...

Please review the DaVinci Notification FHIR IG for preconditions and assumptions.

General workflow : 

Image Modified

Scenarios

Admit and Discharge Use Case Scenarios

...

event code = notification-admit - UPDATE AFTER terminology changes have been applied

Encounter.class code = EMER or IMP 

...

event code = notification-discharge - UPDATE AFTER terminology changes have been applieddischarge

encounter.hospitalization.dischargeDisposition  = any from  http://terminology.hl7.org/CodeSystem/discharge-disposition

...

event code = notification-transfer - UPDATE AFTER terminology changes have been appliedtransfer

encounter.hospitalization.dischargeDisposition  = any from  http://terminology.hl7.org/CodeSystem/discharge-disposition

...

event code = notification-admit - UPDATE AFTER terminology changes have been appliedadmit

encounter code = OBSENC

(Encounter.type may not be known when the notification is sent.  If data is not available  use the appropriate “unknown” concept code from the value set SNOMED SCTID: 261665006 | Unknown (qualifier value))

...

event code = notification-admit - UPDATE AFTER terminology changes have been appliedadmit

encounter code = AMB or SS

...

event code = notification-admit - UPDATE AFTER terminology changes have been appliedencounter code = admit

encounter code = AMB

(Encounter.type may not be known when the notification is sent.  If data is not available  use the appropriate “unknown” concept code from the value set SNOMED SCTID: 261665006 | Unknown (qualifier value))

...

Link

Source Profile

Path

Target Profile

Min

Max

Must Support

1

Da Vinci Notification MessageHeader Profile

MessageHeader.focus

US Core Encounter Profile

1

1

true

2

US Core Da Vinci Notification Encounter Profile

Encounter.location

US Core Location Profile

1

*

true

3

US Core Encounter Da Vinci Notification Encounter Profile

Encounter.participant.individual

US Core Practitioner Profile

0

*

true

4

US Core Da Vinci Notification Encounter Profile

Encounter.subject

US Core Patient Profile

1

1

true

5

Da Vinci HRex Coverage Notification Coverage Profile

Coverage.beneficary

US Core Patient Profile

0

1

true

6

US Core Condition Da Vinci Notification Condition Profile

Condition.encounter

US Core Encounter Profile

0

*

true

7

Da Vinci Notification MessageHeader Profile

MessageHeader.sender

US Core Practitioner Profile|US Core PractitionerRole Profile|US Core Organization Profile

0

1

true

8

Da Vinci Notification MessageHeader Profile

MessageHeader.responsible

US Core Practitioner Profile|US Core PractitionerRole Profile|US Core Organization Profile

0

1

true

9

Da Vinci Notification MessageHeader Profile

MessageHeader.author

US Core Practitioner Profile|US Core PractitionerRole Profile

0

1

true

...

Consider using the “custom" system scope:  system/process-message.write


Bonus 3: Intermediary Forwarding Messages (Acting as Sender with Provenance)

Following the updated guidance in the Framework section of the guide, forward a message bundle to a Recipient/Intermediary.

  • Create a new message bundle with a new Bundle.id and new MessageHeader.id
  • Update the MessageHeader.sender to reflect the Intermediary as the new Sender
  • Replace the resource in the Bundle with the resource referenced by the updated MessageHeader.sender element.
  • Update the MessageHeader.destination to reflect the new Recipient/Intermediary.
  • Add the appropriate US Core Provenance Resource to the message Bundle as outlined in the guide.

( this is demonstrated in the Da Vinci Notification Sender Simulation)


Bonus 4Follow up Queries for more information:

...