0.2.3 - ci-build
servicewellfhirflc, published by Service Well AB. This guide is not an authorized publication; it is the continuous build for version 0.2.3 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/servicewell/servicewell.fhir.flc/ and changes regularly. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define logic, asset collections and other libraries as part of content in this implementation guide.
| FLC Liquid Templates |
This library includes the LIQUID-templates and source sampledata used in this FLC-IG |
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| FLC Source Patient |
This logical model defines the Patient source structure for test with FLC. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| FLC Library |
Profile for Library used together with the FHIR Liquid Converter (FLC). Includes the liquidtemplate folder content as a base64 binary attachments. From this FLC-Library profile its possible to create the template folder structure neddened for the FHIR Liquid Converter to work. |
| FLCStructureMap |
Profile for StructureMap used together with the FHIR Liquid Converter. Includes metadata specifying which Liquid template and FHIR package are used, along with external terminology dependencies required for the conversion to function correctly. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Attachment Folder Structure |
An extension to describe the logical folder structure and file name of an attachment used in Library.content or Binary resources. |
| External Terminology Dependency |
Declares an external dependency on a terminology package (FHIR NPM) that is required for the conversion process to function correctly, but which is not included in the current Implementation Guide. Used to enable automatic retrieval and loading of the required package into a Terminology Server such as Ontoserver. |
| FhirLiquidMap |
Extension used to specify which Liquid template and package should be used for mapping in a StructureMap. |
These define sets of codes used by systems conforming to this implementation guide.
| All Codes from Example Gender CodeSystem |
Example ValueSet that defines gender values for mapping purposes. |
These define new code systems used by systems conforming to this implementation guide.
| Example Gender CodeSystem |
Example CodeSystem that defines gender values for mapping purposes. |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| EHR Source System Patient Identifier |
Example NamingSystem for patient IDs originating from a fictional EHR source system. |
These define transformations to convert between data structures used by systems conforming to this implementation guide.
| FLC Patient to FHIR |
Example Structure Map |
These define transformations to convert between codes by systems conforming with this implementation guide.
| Mapping from gender-example to AdministrativeGender |
ConceptMap showing how the local gender-example CodeSystem maps to FHIR AdministrativeGender. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example FLC transformed Patient |
Example of a Patient resource generated through the FLC-transform process, which maps non-FHIR source data (e.g., JSON or XML structures) into FHIR using Liquid templates. This example illustrates the conversion of a patient record with local identifiers and multiple contact numbers. The source data contained fields such as PatientId, MRN, FirstName, LastName, Phone Number, Gender, DOB, and TimeOfDeath. Through the transform: MRN is mapped to identifier.type = $v2-0203#MR Local PatientId is mapped to a secondary identifier under a system URI for the source system Phone Number values are emitted as multiple telecom elements DOB and TimeOfDeath are converted to FHIR date/time formats The resulting instance demonstrates how the FLC engine normalizes heterogeneous patient data into a consistent FHIR representation. |