Inera Core Implementation Guide
0.2.0 - ci-build
Sweden
Inera Core Implementation Guide - Local Development build (v0.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
This page lists the ConceptMaps defined in this Implementation Guide for mapping between TKB services and FHIR resources.
ConceptMaps provide mappings between TKB domain information models and FHIR resource structures, demonstrating how Swedish national healthcare data from legacy TKB services can be represented using modern FHIR standards.
Mapping from GetAccessLogsForPatient TKB to FHIR AuditEvent. 4-group pattern: query params, AuditEvent, Provenance, unmapped. 32+ elements covering PDL access logs, who accessed what when.
Complete mapping from GetActivities TKB service to FHIR Procedure resource
Complete mapping from GetAlertInformation TKB service to FHIR AllergyIntolerance and Flag resources
Mapping from GetBlocks TKB to FHIR Schedule/Slot. 4-group pattern: query params, Schedule, Provenance, unmapped. 28+ elements covering appointment scheduling blocks, availability.
Complete mapping from GetCareContacts TKB logical model to FHIR Encounter and Provenance resources
Complete mapping from GetCareDocumentation TKB service to FHIR DocumentReference, Composition, and Provenance resources
Mapping from GetCarePlan TKB to FHIR CarePlan. 4-group pattern: query params, CarePlan, Provenance, unmapped. 42+ elements covering care plan activities, goals, participants.
Complete mapping from GetDiagnosis TKB service to FHIR Condition and Provenance resources
Mapping from GetFunctionalStatus TKB to FHIR Observation. 4-group pattern: query params, Observation, Provenance, unmapped. 30+ elements covering functional assessments, ADL, mobility.
Mapping from GetImagingOutcome TKB to FHIR ImagingStudy/DiagnosticReport. 4-group pattern: query params, ImagingStudy, Provenance, unmapped. 35+ elements covering radiology reports, DICOM series, modalities.
Mapping from GetLaboratoryOrderOutcome TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.
TKB Service: GetLaboratoryOrderOutcome v3.0 TKB Domain: clinicalprocess:healthcond:actoutcome v3.0 Logical Model: GetlaboratoryorderoutcomeResponseLM (from FSH-konvertering.xlsx) FHIR Resources: DiagnosticReport, Observation, Specimen Pattern: 4-group (query params, DiagnosticReport, Provenance, unmapped) Coverage: 40+ elements covering lab results, specimen, reference ranges
Mapping from GetMaternityMedicalHistory TKB to FHIR Observation/Condition/Procedure. 4-group pattern: query params, Observation, Provenance, unmapped. 45+ elements covering pregnancy, delivery, prenatal care.
Mapping from GetMedicationHistory TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.
TKB Service: GetMedicationHistory v2.0
TKB Domain: clinicalprocess:activityprescription:actoutcome v2.0
Logical Model: GetMedicationHistoryLM (from FSH-konvertering.xlsx)
FHIR Resources: MedicationStatement, MedicationRequest, Medication
Mapping Coverage: 50+ elements across medication data, prescriptions, dosage Pattern: 4-group approach (query params, MedicationStatement, Provenance, unmapped) Note: Dosage mappings are comprehensive but complex; prioritize prescription and medication product
Complete mapping from GetObservations TKB service to FHIR Observation and Provenance resources
Mapping from GetPersonsForProfile TKB to FHIR Person/RelatedPerson. 4-group pattern: query params, Person, Provenance, unmapped. 25+ elements covering person demographics, relationships.
Mapping from GetReferralOutcome TKB to FHIR ServiceRequest. 4-group pattern: query params, ServiceRequest, Provenance, unmapped. 38+ elements covering referrals, priority, reason, requester.
Mapping between DocBook elements supported by 1177 Inkorg and FHIR Narrative.div XHTML.
DocBook is the required format for 1177 Inkorg messages (AddMessage.Message.Text), but FHIR uses Narrative.div with a restricted XHTML subset (FHIR Narrative data type).
Source: DocBook subset supported by 1177 Inkorg
Target: FHIR Narrative XHTML (limited XHTML 1.0 Strict subset)
FHIR Narrative Constraints:
Reference:
Each ConceptMap follows a consistent pattern:
For detailed guidance on the mapping strategy, see the Mapping Strategy page.