Consolidate LFH Processor Implementations

LinuxForHealth / docs

Linux For Health Documentation

https://LinuxForHealth.github.io/docs

4 stars 3 forks source link

Consolidate LFH Processor Implementations #24

Closed dixonwhitmire closed 4 years ago

dixonwhitmire commented 4 years ago

Each LFH route utilizes a separate "metadata" processor for setting the fields for the LFH "meta data" sub-document. We can consolidate this operation to a single processor and integrate it with the Kafka direct endpoint so that developers don't need to roll as much code.

dixonwhitmire commented 4 years ago

Common metadata fields for data storage:

topic name
timestamp
routeUrl
dataStoreUri
dataFormat
uuid
resourceType

Processors setting metadata values:

AcdAnalyzeProcessor
BlueButton20MetadataProcessor
BlueButton20ResultProcessor
FhirR4MetadataProcessor
Hl7v2MetadataProcessor

These are all evaluated in LinuxForHealthMessage

dixonwhitmire commented 4 years ago

ToDo:

Rename routeUrl to routeUri
create logback-test.xml
Create LinuxForHealthProcessor to set MetaData for LinuxForHealthMessage instances
Create route tests
Update HL7, FHIR, and ACD routes

dixonwhitmire commented 4 years ago

After trying a few things and chatting with the team, we will:

utilize a single class for the LinuxForHealth message metadata
implement other processors "in-line"