Output Pipeline
It doesn’t matter what format the data had when it was ingested into the Health Data Model, once there it is broken down into its component parts with all the logical relationship links created. This means that you can get your data out in any format you need. The data is extracted, shaped and formatted into the required standard, and delivered to where you need it.
Features
Outputs any format - extracts data from the Health Data Model and outputs it in any format (FHIR, HL7, CCD, CSV etc).
Pre-built extensible pipelines - come with the mapping and configuration ready to go, with the ability to extend or build your own pipelines, or tweak an existing one.
How it works
Configuration
Like the ingest pipelines, output pipelines are specifically configured for each type of export format. Choose from a pre-built list of formats, or extend and make your own.
The following tools are used to understand and configure your platform:
Environment Manager - the interface to manage your data providers, data items, and pipeline configurations in your Orchestral environment. Choose from a list of pre-built pipelines to get up and running quickly.
Data Catalogue - browse and understand your Health Data Model. Vital for knowing where to collect your data from.
Output pipeline services
Once configured, you can start outputting data through your output pipelines.
Each service in the pipeline has a specific task.
Extractor
A request or scheduled event triggers the pipeline to extract the required data from the Health Data Model and save it into a dataset in the Data Lake.
Mapper
The mapper will shape the data into the required format - assembling it from all the individual pieces of data that were extracted into one single JSON. It will also translate any codes (valuesets or vocabularies) into the output format.
Parser
This service takes the JSON and formats it into the final output - FHIR, HL7, CCD, CSV etc.
Delivery
The output is securely delivered to the intended destination - whether that is an S3 bucket, Kafka stream, API endpoint, or elsewhere.
Terminology
If required, the terminology service (Code Resolver) will translate any codes to the export format.