You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the implementation selects the HEDA setting by setting HEDA=true we need to be able to build a consistent event across ALL iDaaS-Connect components.
the following attributes will need to be populated:
component: specific component name that is processing data into an event (HL7, Cloud, EDI, ThirdParty, FHIR, etc.)
app: based on the application that has sent in the data to the iDaaS Connect platform
organization: organization the data came from, this is usually found within the data being processed
industrystd: the specific industry standard being processed. Can be anything from HL7, FHIR, CSV, etc.
transactiondate: date the message was created by the system
transactiontime: time the message was created by the system
industrystdevent: the industry specific event (ADT_A01, Appointment, 837, etc.)
data: the event in its entirety
This event should be persisted as a JSON document within kafka when persisted
The text was updated successfully, but these errors were encountered:
When the implementation selects the HEDA setting by setting HEDA=true we need to be able to build a consistent event across ALL iDaaS-Connect components.
the following attributes will need to be populated:
This event should be persisted as a JSON document within kafka when persisted
The text was updated successfully, but these errors were encountered: