# FHIR Modeling, Profiles, and Standards ## Custom Resource Modeling 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. ## Data Mapping Process The Data Mapping process is essential for transforming health data into a format that is both interoperable and aligned with the [FAIR principles](https://build.fhir.org/ig/HL7/fhir-for-fair/)—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. ### Step 1 - Identification 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. ### **Step 2 – Mapping** 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. ### **Step 3 – Implementation** 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 ## Profile and Implementation Guide Support 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. ## Terminology Services 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. ## FHIR Version Support and Migration Strategy 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. ## Collaborative Profiling 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.journl.dk/v1/services/fhir-modeling-profiles-and-standards.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.