The Vital Platform operates best with certain data elements, some of which are not set up for standard data exchange outside of Epic.
This page provides some context around these elements within the patient record and how these can be sent outbound.
34510 ED Disposition
One of the events we look for in a patient's visit is the disposition: is the patient going to be discharged, admitted, or transferred?
This item populates once the provider has selected the patient's disposition. This should trigger an outbound A08 with the disposition mapped to an OBX segment such as below:
OBX|3|TX|ED_DISPO^ED DISPOSITION|1|3|||||||||20240428||||| OBX|3|TX|ED_DISPO^ED DISPOSITION|1|ADMIT|||||||||20240428|||||
We can accept the code, the description, or a combination in OBX.5. If the code is going to be sent then we will need a table of the possible codes and what they correspond to.
34550 Follow Up
A component of our discharge summary feature is surfacing any follow-up appointments a patient needs to make after their visit.
To send this outbound, you will need to create a general table with AIO 91 - Patient Item Mapping specification and then set PV EPT_ITEM_OBX_TBL [5565] with that table.
The table should include the following:
ED MULT FOLLOW UP PROVIDERS [34550] - Format Option: Record Name (2)
ED FOLLOW UP CONTACT INFO [34551]
ED FOLLOW UP SUMMARY [34552]
ED FU OUTSIDE POS [34555] - Format Option: Record Name (2)
ED FOLLOW UP DEPARTMENTS [34558] - Format Option: Record Name (2)
ED FOLLOW UP DATE [34562]