Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Event Driven Processing - HEDA #69

Open
balanscott opened this issue Jan 11, 2023 · 0 comments
Open

Event Driven Processing - HEDA #69

balanscott opened this issue Jan 11, 2023 · 0 comments
Assignees
Labels
cloud native Cloud Native enhancement New feature or request

Comments

@balanscott
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud native Cloud Native enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants