Concept Maps

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 v2.0 TKB service to FHIR DocumentReference and Provenance resources.

TKB Service: GetCarePlan v2.0
TKB Domain: clinicalprocess:logistics:logistics v2 Logical Model: GetcareplansResponseLM FHIR Resources: DocumentReference (primary), Provenance (metadata)

Mapping Coverage:

• ✅ Header metadata: 15+ elements (document ID, title, patient, author, signer, care contact)
• ✅ Document content: Multiple attachments with mediaType (text/plain, text/html, image/png, image/jpeg, image/tiff, application/pdf)
• ✅ Plan metadata: Type of care plan (SIP, SPLPTLRV, SPU, VP, HP, RP, GP, SVP), participating care units
• ✅ Access control: approvedForPatient flag for patient portal visibility

Care Plan Types (typeOfCarePlan):

• SIP - Samordnad individuell plan (Coordinated individual plan)
• SPLPTLRV - Samordnad plan enligt LPT eller LRV (Coordinated plan according to Mental Health Act)
• SPU - Samordnad plan vid utskrivning (Coordinated discharge plan)
• VP - Vårdplan (Care plan)
• HP - Habiliteringsplan (Habilitation plan)
• RP - Rehabiliteringsplan (Rehabilitation plan)
• GP - Genomförandeplan (Implementation plan)
• SVP - Standardiserad vårdplan (Standardized care plan)

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 v2.0 TKB service to FHIR MedicationStatement and Provenance resources.

TKB Service: GetMedicationHistory v2.0
TKB Domain: clinicalprocess:activityprescription:actoutcome v2.0 Logical Model: GetMedicationHistoryResponseLM FHIR Resources: MedicationStatement (primary), Medication, Provenance (metadata)

Mapping Coverage:

• ✅ Header metadata: 20+ elements (document ID, patient, author, signer, care contact)
• ✅ Prescription data: 15+ elements (prescription ID, type, status, reason, treatment period)
• ✅ Drug information: NPL-ID, ATC codes, strength, pharmaceutical form
• ⚠️ Dosage: High-level mapping (detailed dosage structures in Dosage datatype are complex)

Note: Dosage mappings cover core structures (setDosage, conditionalDosage, rampedDosage) but detailed sub-elements require careful transformation according to FHIR Dosage datatype specification.

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:

• Only specific XHTML tags allowed: div, span, p, h1-h6, a, ul, ol, li, dl, dt, dd, b, i, u, em, strong, table, etc.
• All content must be in a single <div xmlns='http://www.w3.org/1999/xhtml'> root
• No DocBook-specific elements (article, section, emphasis[@role]) in output
• Custom styling via @class or @style attributes where needed

Reference:

• https://inera.atlassian.net/wiki/spaces/OIIK/pages/3590029598/Docbook-formatering+av+meddelande
• https://inera.atlassian.net/wiki/spaces/OIIK/pages/3590619160/DocBook+exempel
• http://hl7.org/fhir/R4/narrative.html#Narrative