FHIR Modeling, Profiles, and Standards
Last updated
Last updated
Journl Streamed uses a metadata-driven modeling framework with internal meta-resources (e.g., Entity, Attribute, and Profile) to describe resource schemas. This allows dynamic customization of FHIR structures while maintaining compatibility with the FHIR specification.
The Data Mapping process is essential for transforming health data into a format that is both interoperable and aligned with the —Findable, Accessible, Interoperable, and Reusable. By leveraging the HL7 FHIR standard, this process ensures that health data is structured in a way that supports seamless integration and reusability across systems.
In this step, we gain a deep understanding of the source system's schema and the business processes behind the data. This includes analyzing data granularity, identifying key business metrics, and evaluating whether the data can be standardized using established terminology systems.
Next, source data is mapped to the FHIR standard. This involves aligning elements with the appropriate FHIR resources, profiles, and extensions. Mapping is tailored to geographical standards where applicable, and supported by documentation like the FHIR Resource Index.
Mapped data is integrated into Journl Streamed’s infrastructure, ensuring adherence to relevant FHIR constraints. Both FHIR and non-FHIR datasets are supported, and all transformations are documented to meet the FAIR principles
Custom and standard HL7 Implementation Guides (IG) can be loaded to enforce profiles, constraints, and terminology bindings. Journl Streamed interprets these profiles to enforce validation logic, resource structure, and search behavior.
FHIR extensions are treated as "first-class citizens": they are indexed, queryable, and integrated directly into the data model, offering both flexibility and performance.
Journl Streamed includes a built-in terminology service capable of validating and translating codes across major coding systems (SNOMED CT, LOINC, ICD-10, RxNorm). It supports $validate-code, $expand, and $translate operations, and can integrate with external terminology servers when needed.
Journl Streamed supports FHIR versions R4, R4B, R5, and draft R6. Versioning is managed at the configuration level, and migrations involve bulk export/import flows with support for custom transformation logic. Schema definitions and validation logic are versioned and loaded per environment, enabling controlled rollout of new versions.
All modeling assets—profiles, extensions, mappings, terminologies—are maintained as code in version-controlled repositories. This allows distributed teams to collaborate on data standards with full audit trails, testing workflows, and consistent deployment processes.