The connect-r-and-d from linuxforhealth

Linux for Health Development Documentation

Provide documentation focused on Linux For Health Development. Topics include:

"Hello World" example using the file component
How to Author and use a new component
How to add dependencies for components not included within camel-core, hl7, or "fhir"

Integrate IPFS for data storage

Be able to store records via IPFS.

Support OpenShift 4.x Deployment With OC CLI QuickStart

Create a "quick start" script to provision LFH services and applications on Open Shift using the "oc" CLI with it's "reasonable defaults"

Ethereum Integration w/ Web3j

https://camel.apache.org/components/latest/web3j-component.html

Create REST Callback for MLLP Transactions

Implement the EIP Control Bus Pattern For Route Administration and Monitoring

Implement the EIP control bus pattern to support starting/stopping routes while the application is running.
https://camel.apache.org/components/latest/controlbus-component.html

Add Baseline Protocol support

Add privacy-preserving inter-enterprise public messaging bus support

Create Linux For Health Connect UBI Image

Validate Data Processing Security

Review consumer and producer configurations to ensure that:

data is secured at transit and at rest.
authentication and authorization controls are in place

Camel Route Error Handling

Update the route processing workflow to include an error handler which directs messages to a "dead letter queue/topic".

Linux for Health Connect Continuous Integration

Implement a continuous integration process which executes the Linux for Health test suite when a PR is submitted on GitHub.

Features include:

CI process checks out the proposed branch and executes the test suite
Errors, if any, are displayed on the PR. PRs in an error state may not be merged.
A successful test run is displayed on the PR. PRs without errors may be merged.

Support PodMan Configuration for Local RHEL Deployment

Support configurable builds

Build only a subset of routes to limit dependencies and limit the size of the image.

Infrastructure Support

Support:

container configurations for local development and deployments
provisioning Open Shift on "selected" platforms
initial CI to execute against submitted GitHub PRs

Linux for Health OpenID Connect/OAuth2 Support

Update Linux for Health to support the user authentication and authorization using the OpenID and OAuth2 standards.

Features:

Linux for Health supports user account creation and profile updates (user demographics)
User demographics include: email, first name, last name, and organization
Users are required to authenticate prior to utilizing a Linux for Health processing route
Determine if OpenID/OAuth2 flows can be encapsulated and utilized for end-user authentication/authorization and route based authentication/authorization (see Blue Button)

Use protobuf to serialize data to Kafka

Use protobuf for flexibility and speed

Support secure inbound/outbound LinuxForHealth communications

Support secure inbound/outbound communications using the following:

TLS/x509 certificates
Standard store/directory for certificates, keys, and other assets

Support Health Checks

Update Linux for Health to support the the three healthchecks Camel provides "out of the box"

context
routes
registry

https://camel.apache.org/manual/latest/health-check.html

Add support for Kong

Support Kong for API layer and load balancing. Define the LFH API in Kong, which removes the burden of filtering out "bad" traffic to Kong, which is the point of an API Gateway.

Deserialize to multiple formats based on the messaging target

Enable deserialization of data from Kafka into multiple notification formats based on the downstream messaging target.

Create direct route for data storage and messaging

Encapsulate the data storage and messaging steps in a direct route.

Property File Validation

Integrate property file validation so that warnings or errors are reported prior to application startup.

External FHIR Server Integration and Data Transformation

Update the FHIR R4 route to support transmission to multiple destinations including FHIR Server, SQL on FHIR, etc.
Generate data destinations/targets using Camel EIP - (maybe routing slip?)

Add Role-Based Access Control support

Add support for consent management via Role-Based Access Control [RBAC]

Migrate from NATS Server to NATS JetStream

JetStream is built on/integrated with NATS 2.0 and supports the existing NATS 2.0 security mechanisms, including TLS, NKEYs, etc. So we should be able to integrate with JetStream now.

Simplify LFH Connect Application Property Usage

The property configuration and parsing is a bit complex. Let's reduce the complexity by reducing to a single URI setting so that we can the property placeholder's provided by Camel's simple expressions.

Update Camel Version to 3.4.0

Update our Camel version to 3.4.0 to support recent changes we made to the upstream project for package scanning.

Linux for Health CD Pipeline

The Linux for Health CD pipeline creates and uploads a Linux for Health connect image to Dockerhub when a new release is generated.

Features

The CD pipeline checks out the release tag and executes tests.
If tests are successful, a new image is built and uploaded to Dockerhub.
If errors occur they are reported back to the development team.

Update Java Containers to Support JEP123/Configurable Secure Random-Number Generation

Review https://openjdk.java.net/jeps/123 to determine if the Linux for Health base java container can utilize the default /dev/random generator rather than /dev/urandom. Historically containerized java applications have specified /dev/urandom as a system property to resolve issues with application startups.

Define Common JSON Messaging Format

Define a common JSON messaging format to encapsulate the messages received within a Linux for Health processing route. The messaging format will support message metadata, including provenance, as well as a common key for the messaging/data payload.

Review Camel Metadata fields/headers to see if there is data of value to include in the messaging format.

It would be great if we could include the route id and data format within each message.

Be able to run Camel without all routes being up

This will allow Camel to start even if a component-connected service is down.

x509 Client Certificate Validation

Support Client Certificate Validation Within LFH using x509 client certificates.

Support targeted platforms

Support LinuxOne, AWS, Azure & IoT deployments

AWS
Elastic Container Service - https://aws.amazon.com/ecs/
K8's https://aws.amazon.com/eks/
OpenShift https://aws.amazon.com/quickstart/architecture/openshift/

Azure
Azure Container Service https://azure.microsoft.com/en-us/product-categories/containers/
Azure K8's https://azure.microsoft.com/en-us/services/kubernetes-service/
OpenShift https://www.openshift.com/products/azure-openshift

Linux One - Openshift https://www.ibm.com/it-infrastructure/linuxone/capabilities/linux-containers

IoT - Use a Raspberry Pi for a reference deployment

Implement support for Blue Button 2.0

Implement a route for Blue Button 2.0. Handle authorization and conversion from FHIR R3 to R4.

Support amd64 and s390x architectures for LFH connect

The s309x architecture is required for LinuxOne VMs

Allow contributed docker images for testing

Allow for additional docker-compose.yml files for component-connected services beyond Kafka and NATS.

Document Jasypt encryption processes

consider including guidance on using an env var for Jasypt master password, e.g. sysenv:CAMEL_ENCRYPTION_PASSWORD.

Add Hyperledger Avalon and Linux Foundation Confidential Compute Consortium (CCC) support

Postgres Integration

Include Postgres SQL as a Linux for Health integration option.

Features:

Support the secure storage of Postgres SQL credentials within the application.properties file.
Allow routes to save data to specific schemas.

Notes:

Target schemas are expected to be present prior to integration.
Linux for Health uses Postgres to support OpenID Connect/OAuth2 in an "internal" schema.

MVP Support

Support the following for MVP:

~~HL7 2.x messaging formats~~
~~FHIR R4 messaging formats~~
~~Blue Button CMS integration~~
~~Consolidated error handling and data storage~~
~~Convention over Configuration development~~
CCD message processing
FHIR Server integrations

Add DiCom Connectors

we need to figure out the best mode DICOM and PAC connectors for image processing.

https://github.com/pixmeo/osirix

https://medevel.com/10-open-source-pacs-dicom/

User Authentication With OpenID Connect and OAuth2

In addition to user authentication, provide Camel route-level authorization using OAuth2 scopes.

Generate LPR from data store

Generate the longitudinal patient record from the data store records.

Auditing via NATS Event Stream

Use NATS messaging to track every event that occurs in Linux for Health.

Features:

Use a NATS audit topic per Kafka topic.
Provide a method/create a utility to view a single time-sequenced set of transactions across all NATS audit topics (e.g. docker-compose logs). Alternately, consider 1 NATS audit topic for all LFH events & evaluate pros/cons.

Create some base level of De-ID for Kafka

we need to ascertain the De-ID at the KAFKA level. need a baseline approach such at ARK which is apache 2.0

https://arx.deidentifier.org/downloads/

Update NATS Server Messaging to Support at-least-once Delivery With NATS Jet Stream

The current camel component for NATS messaging supports at-most-once delivery. To mitigate this, add Camel support for NATS JetStream. JetStream is the NATS.io persistence engine that will support streaming as well as traditional message and worker queues for At-Least-Once delivery semantics.
https://github.com/nats-io/jetstream

linuxforhealth / connect-r-and-d Goto Github PK

connect-r-and-d's People

Contributors

Stargazers

Watchers

Forkers

connect-r-and-d's Issues

Recommend Projects

Recommend Topics

Recommend Org