linuxforhealth / edi Goto Github PK

Implement the REST API layer for LinuxForEDI which is used to wrap the xWorkflows transitions.

Endpoints include:

• /analyze [POST] - runs analyze
• /enrich [POST] - runs analyze, enrich
• /validate [POST] - runs analyze, validate
• /translate [POST] - runs analyze, translate
• /process [POST] - runs all workflow steps

Support the following post parameters:

• async: boolean - True/False: indicates if processing is async, requiring a callback URL when results are complete
• edi: string - the edi message

LinuxForHealth EDI provides a standard workflow for parsing, validating, and publishing standard health care data regardless of format.

The LinuxForHealth EDI CLI is named "cli" which may run into naming collisions. We should rename the cli to lfhedi as that is a more descriptive name.

Placeholder issue for HL7 2.6 Development Library Development.

Update the EDI project's Development Quickstart and Tooling to support the Developer Certificate of Origin.

Example: IBM FHIR Server

Create an EDI Exception object so that we can raise exceptions, provide stack traces, and chained exceptions.

Placeholder issue for X12 Development Library Development.

Complete Quickstart Support by adding additional data samples and support for C-CDA in the "analyze" transition of the workflow.

Add trivial/hello world type of samples to the edi/samples directory:

• C-CDA
• FHIR R4 Patient
• HL7 2.6

Update the analyze transition to support C-CDA detection.

Validate using the CLI and "SDK" as shown in the current Quickstart.

Update setup.cfg to support "more tolerant" version ranges where we are >= a minimum version and don't check an upper bound.

Placeholder issue for FHIR R4 Development Library Development.

Placeholder issue to track C-CDA library development

Create a Dockerfile to support a lightweight container for the EDI application, supporting the REST API and CLI integration modes.