Da Vinci Unsolicited Notifications
1.1.0-preview - STU 1.1 Preview United States of America flag

Da Vinci Unsolicited Notifications, published by HL7 International / Infrastructure And Messaging. This guide is not an authorized publication; it is the continuous build for version 1.1.0-preview built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-alerts/ and changes regularly. See the Directory of published versions

ConceptMap: Direct ADT to Da Vinci Alerts ConceptMap

Official URL: http://hl7.org/fhir/us/davinci-alerts/ConceptMap/direct-alerts Version: 1.1.0-preview
Standards status: Trial-use Maturity Level: 2 Computable Name: DirectAlerts
Other Identifiers: OID:2.16.840.1.113883.4.642.40.47.18.1

Copyright/Legal:

  1. This material contains content from LOINC (http://loinc.org). LOINC is copyright \xA9 1995-2020, Regenstrief Institute, Inc. and the Logical Observation # Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC\xAE is a registered United States trademark of Regenstrief Institute, Inc.
  2. This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.

Since May 1, 2021 CMS requires that hospitals send notifications electronically for admit, transfer and discharge events to the patient's care team members, for which most implementations currently use V2 ADT messages. As a result DirectTrust, a consensus body of forty organizations and individuals representing the care continuum, collaborated in creating an Implementation Guide using Direct Secure Messaging for both senders and receivers. The Event Notifications via the Direct Standard® defines the necessary data element to cover the CMS rules, maps those to the V2 elements in several ADT message structures and provides the value sets for coded elements.

These V2 elements have been mapped them to their respective location in this DaVinci FHIR IG for the Admit-Transfer-Discharge Use case. In addition, the value set concepts between the two product families have been mapped, where possible.

This ConceptMap summarizes the Direct ADT message to the Da Vinci Notification Terminology Mappings. Complete mappings can be downloaded as an excel file at https://hl7.org/fhir/us/davinci-alerts/tables/DirectToDaVinciMap.xlsx.

Generated Narrative: ConceptMap direct-alerts

Mapping from https://directtrust.org/what-we-do/direct-secure-messaging to http://hl7.org/fhir/us/davinci-alerts/ImplementationGuide/hl7.fhir.us.davinci-alerts


Group 1 Mapping from Logical Observation Identifiers, Names and Codes (LOINC) to Da Vinci Event CodeSystem Notification

Source CodeRelationshipTarget CodeComment
86530-3 (Visit notification)is equivalent tonotification-referral (Referral Notification)
86532-9 (Admission notification)is equivalent tonotification-admit (Admit Notification)Alerts terminology doesn't distinguish types of sevice locations
98141-5 (Emergency department Admission notification)is equivalent tonotification-admit (Admit Notification)
79429-7 (Hospital Admission notification)is equivalent tonotification-admit (Admit Notification)Alerts terminology doesn't distinguish between in and out patients
79430-5 (Hospital Discharge notification)(not mapped)
80110-0 (Emergency department Visit notification)(not mapped)
98143-1 (Emergency department Arrival notification)(not mapped)
86532-9 (Admission notification)(not mapped)
98144-9 (Emergency department Departure notification)(not mapped)
86531-1 (Discharge notification)is equivalent tonotification-discharge (Discharge Notification)
98142-3 (Emergency department Discharge notification)(not mapped)
98145-6 (Outpatient Visit notification)is equivalent tonotification-outpatient-visit (Outpatient Visit Notification)

Group 2 Mapping from patientClass to ActCode

Source CodeRelationshipTarget CodeComment
E (Emergency)is equivalent toEMER (emergency)
I (Inpatient)is equivalent toIMP (inpatient encounter)
O (Outpatient)is equivalent toAMB (ambulatory)
P (Preadmit)is equivalent toPRENC (pre-admission)
R (Recurring patient)(not mapped)
B (Obstetrics)(not mapped)
C (Commercial Account)(not mapped)
N (Not Applicable)(not mapped)
U (Unknown)(not mapped)
I (Inpatient)is equivalent toACUTE (inpatient acute)If this is needed in Direct Trust, can consider expanding the value set
I (Inpatient)is equivalent toNONAC (inpatient non-acute)If this is needed in Direct Trust, can consider expanding the value set

Group 3 Mapping from unspecified code system to ActCode

Source CodeRelationshipTarget CodeComment
S (Short Stay)is equivalent toSS (short stay)S is an extension to the base PV1-2 patientClass value set in V2
V (Observation)is equivalent toOBSENC (observation encounter)V is an extension to the base PV1-2 patientClass value set in V2

Group 4 Mapping from providerRole to ParticipationType

Source CodeRelationshipTarget CodeComment
AD (Admitting)is equivalent toADM (admitter)Also in PV1-17 Admitting Doctor in v2
AT (Attending)is equivalent toATND (attender)Also in PV1-7 Attending Doctor in v2
CP (Consulting Provider)is equivalent toCON (consultant)Also in PV1-9 Consulting Doctor
FHCP (Family Health Care Professional)(not mapped)
PP (Primary Care Provider)(not mapped)
RP (Referring Provider)is equivalent toREF (referrer)Also in PV1-8 Referring doctor in v2
RT (Referred to Provider)is equivalent toREFT (Referred to)

Group 5 Mapping from unspecified code system to ParticipationType

Source CodeRelationshipTarget CodeComment
TF (Treating Facility)is equivalent toLOC (location)TF is an extension to the base ROL-3 providerRole value set in V2

Group 6 Mapping from administrativeSex to AdministrativeGender

Source CodeRelationshipTarget CodeComment
F (Female)is equivalent tofemale
M (Male)is equivalent tomale
O (Other)is equivalent toother
U (Unknown)is equivalent tounknown
A (Ambiguous)is equivalent tootherSince the binding in USCorePatient is required, will have to map to "other"
N (Not Applicable)is equivalent tootherSince the binding in USCorePatient is required, will have to map to "other"
X (Non-Binary)is equivalent tootherSince the binding in USCorePatient is required, will have to map to "other"

Group 7 Mapping from nameType2 to NameUse

Source CodeRelationshipTarget Code
N (Nickname)is equivalent tonickname
D (Customary Name)is equivalent tousual
L (Official Registry Name)is equivalent toofficial
TEMP (Temporary Name)is equivalent totemp
S (Pseudonym)is equivalent toanonymous
BAD (Bad Name)is equivalent toold
M (Maiden Name)is equivalent tomaiden (Name changed for Marriage)
O (Other)(not mapped)
A (Assigned)(not mapped)
B (Birth name)is equivalent tomaiden (Name changed for Marriage)
C (Adopted Name)is equivalent toofficial
F (Fathers Name)(not mapped)
I (Licensing Name)(not mapped)
K (Business name)(not mapped)
MSK (Masked)is equivalent toanonymous
NAV (Temporarily Unavailable)(not mapped)
NB (Newborn Name)(not mapped)
NOUSE (No Longer To Be Used)is equivalent toold
P (Name of Partner/Spouse)(not mapped)
R (Registered Name)(not mapped)
REL (Religious)(not mapped)
T (Indigenous/Tribal)is equivalent toofficial
U (Unknown)(not mapped)

Group 8 Mapping from admissionType to SNOMED CT (all versions)

Source CodeRelationshipTarget Code
A (Accident)(not mapped)
E (Emergency)is equivalent to4525004 (Emergency department patient visit)
L (Labor and Delivery)(not mapped)
R (Routine)is equivalent to308335008 (Patient encounter procedure)
N (Newborn (Birth in healthcare facility))(not mapped)
U (Urgent)(not mapped)
C (Elective)(not mapped)

Group 9 Mapping from diagnosisType to Diagnosis Role

Source CodeRelationshipTarget Code
A (Admitting)is equivalent toAD (Admission diagnosis)
W (Working)(not mapped)
F (Final)is equivalent toDD (Discharge diagnosis)

Group 10 Mapping from relationship to RoleCode

Source CodeRelationshipTarget CodeComment
MTH (Mother)is equivalent toMTH (Mother)This is described specifically for the maternal health use case

Group 11 Mapping from telecommunicationUse to ContactPointUse

Source CodeRelationshipTarget CodeComment
PRN (Primary Residence Number)is equivalent tohomeFHIR doesn't distinguish types of homes for contacts
ORN (Other Residence Number)is equivalent tohomeFHIR doesn't distinguish types of homes for contacts
WPN (Work Number)is equivalent towork
VHN (Vacation Home Number)is equivalent tohomeFHIR doesn't distinguish types of homes for contacts
ASN (Answering Service Number)(not mapped)
EMR (Emergency Number)(not mapped)
PRS (Personal)(not mapped)

Group 12 Mapping from telecommunicationUse to ContactPointSystem

Source CodeRelationshipTarget CodeComment
NET (Network (email) Address)is equivalent toemailwould need to map to different datatype element and use different value set
BPN (Beeper Number)is equivalent topagerwould need to map to different datatype element and use different value set

Group 13 Mapping from telecommunicationUse to unspecified code system

Source CodeRelationshipTarget Code
DSM (Direct Secure Messaging)(not mapped)