Equivalent of Epic ED-SOA messages and Smart Data Elements

[Jeffrey Eubanks]

Hello, I have designed an app that works with Epic's FHIR interface and I need to design an equivalent app for Cerner.  Specifically, I need to know the Cerner equivalent of:

1. ED-SOA messages, which is the mechanism by which Epic "pushes" events via HTTP to a subscribed external web service, based on configurable triggers
2. Smart Data Elements which enables hospitals to add a custom field such as "Patient want to opt in to Acme App participation (Yes/No)"

Can someone help me understand what Cerner's equivalents are for these 2 things?

[Stacy Adkins]

Cerner will need to validate that my response in correct, but the custom fields term used in Cerner is UDF (user defined field). These are cutom reg fields that can be configured on the encounter conversations in the registration system. I believe these are supported as part of the encounter resource today. I also don't believe there is current any equivalent to ED-SOA, which is why we use a combo of FHIR and HL7v2 with our integration to Cerner so we can listen for updates in real-time.

[Aaron McGinn (Cerner)]

What Stacy describes is mostly accurate. Depending on the user defined field, it may not be returned through the FHIR resource API.

For subscription event functionality, the latest HL7 FHIR standard is CDS Hooks [1][2], though Cerner's implementation is not yet generally available (GA). The current workaround for this is to use HL7v2 [3] instead, again as Stacy mentioned.

[1] https://cds-hooks.hl7.org/

[2] https://cds-hooks.org/

[3] https://www.hl7.org/implement/standards/product_brief.cfm?product_id=185

-Aaron (Cerner)