Svensk profil f??r l??kemedels??verk??nslighet och allergier baserad p?? TKB GetAlertInformation v2.0.

Profilen st??djer dokumentation av:

• L??kemedels??verk??nslighet (NPL, ATC-kodade)
• F??do??mnesallergier
• Milj??allergier
• Annan ??verk??nslighet

Svensk terminologi:

• NPL (Nationellt Produktregister f??r L??kemedel) - OID: 1.2.752.129.2.1.5.1
• ATC (Anatomisk Terapeutisk Kemisk klassifikation) - OID: 1.2.752.129.2.2.3.1.1
• KV Typ av ??verk??nslighet - OID: 1.2.752.129.2.2.3.10
• KV Allvarlighetsgrad - OID: 1.2.752.129.2.2.3.3
• KV Visshetsgrad - OID: 1.2.752.129.2.2.3.11
• SNOMED CT Swedish Edition

TKB Source: GetAlertInformation v2.0 (clinicalprocess:healthcond:description). Maps TKB alertInformation elements including typeOfHypersensitivity (1..1), degreeOfSeverity (1..1), degreeOfCertainty (1..1), hypersensitivityAgent (1..1), comment (0..1).

Svensk profil f??r ??tkomstloggar baserad p?? TKB GetAccessLogsForPatient v2.0.

Anv??nds f??r PDL-kr??vd ??tkomstloggning:

• Loggning av ??tkomst till patientdata
• V??rdrelation och beh??righetskontroll
• Sp??rbarhet enligt Patientdatalagen

PDL-krav: Obligatorisk ??tkomstloggning enligt Patientdatalagen (SFS 2008:355)

K??lla: TKB GetAccessLogsForPatient v2.0 (ehr:log)

Svensk profil f??r v??rdplaner baserad p?? TKB GetCarePlan v2.0.

Anv??nds f??r:

• V??rdplaner
• Behandlingsplaner
• Rehabiliteringsplaner
• Omv??rdnadsplaner

K??lla: TKB GetCarePlan v2.0 (clinicalprocess:healthcond:description)

Svensk profil f??r kliniska bed??mningar och funktionsstatus baserad p?? TKB GetFunctionalStatus v1.0.

Anv??nds f??r:

• Funktionsstatussammanfattningar
• Kliniska bed??mningar
• Bed??mning av funktionstillst??nd
• Prognos och rekommendationer

K??lla: TKB GetFunctionalStatus v1.0 (clinicalprocess:healthcond:description)

Svensk profil f??r strukturerade kliniska dokument baserad p?? TKB GetCareDocumentation v2.0.

Anv??nds f??r strukturerade dokument med v??ldefinierade sektioner:

• Anamnes (History of Present Illness)
• Status/Unders??kningsfynd (Physical Examination)
• Bed??mning (Assessment)
• ??tg??rd/Plan (Plan)

Narrative Text (text-element): Composition.text kan anv??ndas f??r att tillhandah??lla en helhetsbild av dokumentet i XHTML-format. F??r patient-administrativa meddelanden fr??n 1177 Inkorg (kallelser, bokningar, brev) kan DocBook-formaterat inneh??ll transformeras till FHIR Narrative XHTML enligt ConceptMap DocBook-to-Narrative.

Se DocBook to FHIR Narrative Guide f??r detaljer om:

• Transformation av DocBook emphasis[@role] till XHTML (bold, italics, information boxes, warnings)
• Val mellan Composition.text (presentation-fokuserad) och Composition.section (data-fokuserad)
• Hantering av specialformatering (collapsible sections, variabellistor, f??rgade rutor)

K??lla: TKB GetCareDocumentation v2.0 (clinicalprocess:healthcond:description)

Swedish national base profile for Condition resource. Base profile for all condition/problem/diagnosis resources in Swedish healthcare.

Key Swedish Features:

• ICD-10-SE code system support
• SNOMED CT SE support
• Swedish clinical status codes
• Links to Swedish Patient, Practitioner, Organization profiles

This profile serves as the foundation for more specific profiles like ConditionDiagnosisInera.

Swedish profile for diagnoses as retrieved from GetDiagnosis TKB service. This profile represents the Swedish national requirements for diagnosis documentation.

Mapping from TKB GetDiagnosis v2.0:

• See ConceptMap: ConceptMapGetDiagnosisTKBToCondition
• TKB Service: GetDiagnosis v2.0
• TKB Domain: clinicalprocess:healthcond:description v2.1

Swedish Terminology:

• ICD-10-SE: Swedish edition of ICD-10 classification
• SNOMED CT SE: Swedish edition of SNOMED CT

Key TKB Mappings:

• diagnos.diagnosKod ??? code.coding (ICD-10-SE, 1..1 in TKB)
• diagnos.diagnosDisplayName ??? code.text (1..1 in TKB)
• diagnos.diagnosTid ??? onsetDateTime (1..1 in TKB)
• accountableHealthcareProfessional ??? recorder + Provenance
• healthcareProfessionalCareUnitHSAId ??? encounter.serviceProvider

Svensk profil f??r patientsp??rrar (blocks) baserad p?? TKB GetBlocks v2.0.

Anv??nds f??r att dokumentera:

• Inre sp??rr (inom v??rdgivare)
• Yttre sp??rr (nationell NP??-sp??rr)
• Samtycke och sp??rrar enligt PDL

PDL-kr??vs: Dokumentation enligt Patientdatalagen (SFS 2008:355)

K??lla: TKB GetBlocks v2.0 (ehr:accesscontrol)

Svensk profil f??r unders??kningssvar (laboratorium, radiologi, patologi) baserad p?? TKB.

Anv??nds f??r:

• Laboratoriesvar (GetLaboratoryOrderOutcome)
• Radiologisvar (GetImagingOutcome)
• Patologisvar
• Andra diagnostiska unders??kningar

K??lla: TKB GetLaboratoryOrderOutcome v3.1, GetImagingOutcome v2.0

Svensk profil f??r v??rdkontaktanteckningar och kliniska dokument baserad p?? TKB GetCareDocumentation v2.0.

Anv??nds f??r:

• V??rdkontaktanteckningar
• L??karintyg
• Epikrisutskrivningssammanfattning
• Operationsber??ttelser
• Andra kliniska dokument

K??lla: TKB GetCareDocumentation v2.0 (clinicalprocess:healthcond:description)

Swedish national base profile for Encounter resource. Maps to GetCareContacts TKB service for v??rdkontakter.

Key Swedish Features:

• Swedish encounter classifications via KV V??rdkontakttyp (OID 1.2.752.129.2.2.2.25)
• Care unit identification via HSA-ID
• Links to Swedish Patient and Practitioner profiles
• PDL (Patientdatalag) audit requirements via Provenance

TKB Source: GetCareContacts v2.0/v3.0 (clinicalprocess:logistics:logistics). Maps TKB careContact elements including careContactCode (1..1), careContactTimePeriod (1..1), careContactStatus (1..1), careContactReason (0..1).

Svensk profil f??r varningar och uppm??rksamhetsinformation baserad p?? TKB GetAlertInformation v2.0.

Anv??nds f??r alerttyper som inte ??r l??kemedels??verk??nslighet:

• Allvarlig sjukdom
• Behandlingsvarningar
• Smittsamsjukdom
• Begr??nsning av v??rd
• Ostrukturerade historiska alerter

K??lla: TKB GetAlertInformation v2.0 (clinicalprocess:healthcond:description)

Svensk profil f??r bildunders??kningar baserad p?? TKB GetImagingOutcome v2.0.

Omfattar DICOM-baserade bildunders??kningar:

• R??ntgen (XR)
• Datortomografi (CT)
• Magnetresonanstomografi (MR)
• Ultraljud (US)
• PET/SPECT

K??lla: TKB GetImagingOutcome v2.0 (clinicalprocess:healthcond:actoutcome)

Svensk profil f??r l??kemedelsordinationer och recept baserad p?? TKB GetMedicationHistory v1.2.

Svensk terminologi:

• NPL (Nationellt Produktregister f??r L??kemedel) - OID: 1.2.752.129.2.1.5.1
• ATC (Anatomisk Terapeutisk Kemisk klassifikation) - OID: 1.2.752.129.2.2.3.1.1

TKB Source: GetMedicationHistory v1.2 (clinicalprocess:healthcond:actoutcome). Maps TKB drugArticle elements including articleName (1..1), nplId/atcCode (0..1).

Svensk profil f??r l??kemedelsanv??ndning baserad p?? TKB GetMedicationHistory v1.2.

Profilen st??djer dokumentation av:

• P??g??ende l??kemedelsbehandling
• Historisk l??kemedelsanv??ndning
• Egenv??rd och receptbelagda l??kemedel

Svensk terminologi:

• NPL (Nationellt Produktregister f??r L??kemedel) - OID: 1.2.752.129.2.1.5.1 - prim??rt
• ATC (Anatomisk Terapeutisk Kemisk klassifikation) - OID: 1.2.752.129.2.2.3.1.1

TKB Source: GetMedicationHistory v1.2 (clinicalprocess:healthcond:actoutcome). Maps TKB drugArticle elements including articleName (1..1), nplId/atcCode (0..1).

Svensk profil f??r laboratoriesvar baserad p?? TKB GetLaboratoryOrderOutcome v3.1.

Svensk terminologi:

• NPU (Nomenclature for Properties and Units) - OID: 1.2.752.108.1.1.1 - prim??rt
• LOINC (Logical Observation Identifiers Names and Codes)
• SNOMED CT Swedish Edition

TKB Source: GetLaboratoryOrderOutcome v3.1 (clinicalprocess:healthcond:actoutcome). Maps TKB analysis elements including analysisCode (1..1), analysisValue (1..1), analysisTime (1..1).

Svensk profil f??r vitalparametrar baserad p?? TKB GetObservations v2.0 och FHIR Vital Signs.

Omfattar:

• Blodtryck (systoliskt/diastoliskt)
• Puls/hj??rtfrekvens
• Andningsfrekvens
• Kroppstemperatur
• Syres??ttning (SpO2)
• Kroppsvikt och l??ngd
• BMI

Svensk terminologi:

• LOINC (prim??rt f??r vitalparametrar)
• NPU (kompletterande)
• SNOMED CT Swedish Edition

K??lla: TKB GetObservations v2.0 (clinicalprocess:healthcond:actoutcome)

Swedish national base profile for Organization resource for NP?? (Nationell Patient??versikt). Builds on HL7 Sweden SE base profile and adds NP??-specific requirements.

Inheritance: SE base profile ??? FHIR Organization

Key Swedish Features (from SE base profile):

• HSA-ID for organizations
• Swedish organization types (v??rdgivare, v??rdenhet, etc.)
• Swedish address format

NP??-specific additions:

• PDL organizational hierarchy (v??rdgivare ??? v??rdenhet ??? organisationsenhet)
• TKB service integration requirements

Swedish national base profile for Patient resource for NP?? (Nationell Patient??versikt). Builds on HL7 Sweden SE base profile and adds NP??-specific requirements.

Inheritance: SE base profile ??? IPA patient ??? FHIR Patient

Key Swedish Features (from SE base profile):

• Swedish national ID systems (personnummer, samordningsnummer, reservnummer)
• Swedish address format with official address types
• Swedish name extensions (mellannamn, eget efternamn)
• Swedish marital status codes

NP??-specific additions:

• TKB service integration requirements
• PDL (Patientdatalag) compliance

Swedish national base profile for Practitioner resource for NP?? (Nationell Patient??versikt). Builds on HL7 Sweden SE base profile and adds NP??-specific requirements.

Inheritance: SE base profile ??? FHIR Practitioner

Key Swedish Features (from SE base profile):

• HSA-ID for practitioner identification
• Swedish professional qualification codes (HOSP, SOSNYK)
• Swedish occupational position codes (HSA paTitleCode)

NP??-specific additions:

• TKB service integration requirements (accountableHealthcareProfessional mapping)
• PDL audit requirements

Swedish national base profile for PractitionerRole resource. Links practitioners to their roles and organizations with Swedish HSA-ID system.

Key Swedish Features:

• Role codes from Swedish classification system
• Links to Swedish organizations via HSA-ID
• Care unit associations

Svensk profil f??r aktiviteter/??tg??rder baserad p?? TKB GetActivities v1.3.

Anv??nds f??r:

• Operationer
• Unders??kningar
• V??rd??tg??rder
• Behandlingsinterventioner

K??lla: TKB GetActivities v1.3 (clinicalprocess:activity:actions)

Svenska kodsystem:

• KV?? (Klassifikation av v??rd??tg??rder): OID 1.2.752.116.1.1.1.1.4
• HSA-ID (K??llsystem): OID 1.2.752.129.2.1.4.1
• KV Befattning: OID 1.2.752.129.2.2.1.4

TKB-mappning: Se ConceptMap GetActivities ??? Procedure

Svensk profil f??r m??drah??lsov??rds- och f??rlossningsprocedurer baserad p?? TKB GetMaternityMedicalHistory v1.1.

Anv??nds f??r:

• F??rlossningar
• Graviditetsrelaterade procedurer
• Postpartum-??tg??rder
• Obstetriska ingrepp

Svensk terminologi:

• KV?? (Klassifikation av v??rd??tg??rder)
• SNOMED CT Swedish Edition (obstetrics codes)

K??lla: TKB GetMaternityMedicalHistory v1.1 (clinicalprocess:healthcond:description)

Denna profil ut??kar ProcedureBaseInera med m??drah??lsov??rdsspecifika begr??nsningar.

Swedish national base profile for Provenance resource. Captures authorship and accountability information from TKB document headers.

Key Swedish Features:

• Maps TKB accountableHealthcareProfessional elements
• Captures care unit and care provider information
• Supports PDL (Patient Data Law) audit requirements

Svensk profil f??r remisser och tj??nstef??rfr??gningar baserad p?? TKB GetReferralOutcome v1.0.

Anv??nds f??r:

• Remisser mellan v??rdgivare
• Remisser inom v??rdgivare
• Best??llningar av tj??nster
• Konsultf??rfr??gningar

K??lla: TKB GetReferralOutcome v1.0 (clinicalprocess:activity:request)

Svensk profil f??r arbetsfl??de och uppf??ljning av remisser baserad p?? TKB GetReferralOutcome v1.0.

Anv??nds f??r att sp??ra:

• Remissstatus och handl??ggning
• Arbetsk?? och tilldelning
• Remissutfall och resultat

K??lla: TKB GetReferralOutcome v1.0 (clinicalprocess:activity:request)

Extension f??r att ge renderingshints f??r visuell presentation av Composition.section.

Anv??nds tillsammans med section.code (SectionSemanticType) f??r att indikera hur en sektion kan renderas visuellt, utan att diktera exakt utseende.

Klienter ??r fria att anpassa rendering efter sin UI/plattform (webb, mobil, sk??rml??sare).

K??lla: 1177 Inkorg DocBook emphasis[@role] visual patterns

Categories for conditions including Swedish-specific categories

Codes for conditions - includes ICD-10-SE and SNOMED CT SE

Classification of encounter type

Swedish encounter types (v??rdkontakttyper)

HSA-ID systems for organizations (care providers and care units)

Types of healthcare organizations in Sweden

Swedish healthcare professional qualifications

Swedish healthcare professional roles

Swedish healthcare professional specialties

Activities for provenance tracking

Till??tna renderingshints f??r visuell presentation av dokumentsektioner.

Anv??nds i extension section-presentation-style f??r att ge klienter v??gledning om hur sektionen kan renderas, utan att diktera exakt utseende.

Till??tna semantiska typer f??r dokumentsektioner.

Anv??nds i Composition.section.code f??r att indikera sektionens semantiska betydelse vid transformation av 1177 Inkorg DocBook-meddelanden till FHIR.

Se DocBook to Narrative Guide f??r mappningsstrategi.

Swedish adaptation of ICD-10 classification

Code system for HSA-ID organization identifier types

Renderingshints f??r visuell presentation av dokumentsektioner.

Dessa koder ??r rekommendationer f??r hur en sektion kan visas, inte krav. Olika klienter kan implementera dessa p?? olika s??tt baserat p?? sina UI-riktlinjer.

K??lla: 1177 Inkorg visuella m??nster f??r DocBook emphasis[@role]

Semantiska typer f??r dokumentsektioner baserade p?? DocBook emphasis[@role] fr??n 1177 Inkorg.

Anv??nds f??r att bevara semantisk betydelse vid transformation av DocBook-formaterade patientmeddelanden till FHIR Composition.section, oberoende av visuell presentation.

Anv??ndning:

• Composition.section.code f??r att indikera sektionens semantiska typ
• Tillsammans med extension section-presentation-style f??r renderingshints
• G??r sektioner s??kbara och maskinl??sbara (query by section type)

K??lla: 1177 Inkorg DocBook-formatering, se DocBook to Narrative Guide

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.

Mapping from GetActivities TKB service to FHIR resources. Based on Excel-generated logical models with enhanced field descriptions.

TKB Service: GetActivities v1.3
TKB Domain: clinicalprocess:activity:actions v1.3 Logical Models: GetactivitiesRequestLM, GetactivitiesResponseLM (from FSH-konvertering.xlsx) FHIR Resource: Procedure
FHIR Profile: ProcedureBaseInera

Mapping Coverage:

• ??? Mapped to Procedure: 25+ elements (procedures, operations, examinations)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship)
• ??? Not mapped: 10+ elements (query parameters, result wrapper)

Activity Types:

• Surgical Procedures (Operationer) ??? Procedure
  • Coded with KV?? (Klassifikation av v??rd??tg??rder)
  • Surgical interventions, operations
• Examinations (Unders??kningar) ??? Procedure
  • Diagnostic procedures
  • Clinical examinations
• Interventions (??tg??rder) ??? Procedure
  • Therapeutic interventions
  • Treatment activities

Swedish Code Systems:

• KV?? (Klassifikation av v??rd??tg??rder): OID 1.2.752.116.1.1.1.1.4
• HSA-ID (K??llsystem): OID 1.2.752.129.2.1.4.1
• Personnummer: OID 1.2.752.129.2.1.3.1
• Samordningsnummer: OID 1.2.752.129.2.1.3.3

Mapping from GetAlertInformation TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.

TKB Service: GetAlertInformation v2.0/v3.0
TKB Domain: clinicalprocess:healthcond:description v2.1/v3.0 Logical Model: GetAllertInformationLM (from FSH-konvertering.xlsx) FHIR Resources: AllergyIntolerance (pharmaceutical), Flag (other alerts)
FHIR Profiles: AllergyIntoleranceBaseInera, FlagBaseInera

Mapping Coverage:

• ??? Mapped to AllergyIntolerance: 18+ elements (pharmaceutical hypersensitivity)
• ??? Mapped to Flag: 12+ elements (serious disease, treatment warnings, etc.)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship)
• ??? Not mapped: 5+ elements (query parameters, result wrapper)

Alert Types:

• Pharmaceutical Hypersensitivity (L??kemedels??verk??nslighet) ??? AllergyIntolerance
  • Drug allergy/intolerance with ATC codes
  • Severity: mild, moderate, severe, life-threatening
  • Reaction manifestations
• Serious Disease (Allvarlig sjukdom) ??? Flag
  • Infectious diseases, bleeding disorders, etc.
• Treatment Warnings (Behandlingsvarning) ??? Flag
• Communicable Disease (Smittsam sjukdom) ??? Flag
• Restriction of Care (Begr??nsning av v??rd) ??? Flag
• Unstructured Historical Alerts ??? Flag

Swedish Code Systems:

• KV Typ av ??verkanslighet: OID 1.2.752.129.2.2.3.10
• KV Allvarlighetsgrad: OID 1.2.752.129.2.2.3.3
• KV Visshetsgrad: OID 1.2.752.129.2.2.3.11
• ATC codes: OID 1.2.752.129.2.2.3.1.1 (Swedish ATC)
• NPL (Nordic Pharmaceutical List): OID 1.2.752.129.2.1.5.1

Mapping from GetBlocks TKB to FHIR Schedule/Slot. 4-group pattern: query params, Schedule, Provenance, unmapped. 28+ elements covering appointment scheduling blocks, availability.

Mapping from GetCareContacts TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.

TKB Service: GetCareContacts v2.0/v3.0
TKB Domain: clinicalprocess:logistics:logistics v2.0/v3.0 Logical Model: GetcarecontactsResponseLM (from FSH-konvertering.xlsx) FHIR Resources: Encounter (primary), Provenance (metadata) FHIR Profiles: EncounterBaseInera

Mapping Coverage:

• ??? Mapped to Encounter: 20+ elements (contact details, timing, participants, location, status)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship, organization hierarchy)
• ??? Not mapped: 10+ elements (query parameters, result wrapper, deprecated/unused fields)

Key Patterns:

• careContact ??? Encounter resource
• careContactHeader ??? Provenance resource (authorship tracking)
• careContactBody ??? Encounter clinical elements
• Query parameters ??? Search parameters (not stored in resources)
• Result wrapper ??? Bundle or OperationOutcome

Mapping from GetCareDocumentation TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.

TKB Service: GetCareDocumentation v2.1/v3.0
TKB Domain: clinicalprocess:logistics:logistics v2.1/v3.0 Logical Model: GetcaredocumentationResponseLM (from FSH-konvertering.xlsx) FHIR Resources: DocumentReference (primary metadata), Composition (structure), Provenance (authorship) FHIR Profiles: DocumentReferenceInera, CompositionClinicalNoteInera

Mapping Coverage:

• ??? Mapped to DocumentReference: 15+ elements (document metadata, type, status, content)
• ??? Mapped to Composition: 20+ elements (structured content, sections, attestation)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship, signatures)
• ??? Not mapped: 8+ elements (query parameters, result wrapper, deprecated fields)

Document Types Supported:

• V??rdkontaktanteckningar (clinical notes from encounters)
• L??karintyg (medical certificates)
• Utskrivningssammanfattningar (discharge summaries)
• V??rdplaner (care plans)
• Remisser (referrals) - also has dedicated service
• Journalutdrag (medical record extracts)

Key Patterns:

• careDocumentation ??? DocumentReference (metadata) + Composition (content)
• careDocumentationHeader ??? Provenance (authorship tracking)
• Binary content (PDF/XML) ??? DocumentReference.content.attachment
• Structured content ??? Composition.section
• Query parameters ??? Search parameters (not stored)

Mapping from GetCarePlan TKB to FHIR CarePlan. 4-group pattern: query params, CarePlan, Provenance, unmapped. 42+ elements covering care plan activities, goals, participants.

Mapping from GetDiagnosis TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.

TKB Service: GetDiagnosis v2.0/v3.0
TKB Domain: clinicalprocess:healthcond:description v2.1/v3.0 Logical Model: GetDiagnosisLM (from FSH-konvertering.xlsx) FHIR Resource: Condition
FHIR Profile: ConditionDiagnosisInera

Mapping Coverage:

• ??? Mapped to Condition: 12+ elements (diagnosis code, status, severity, verification)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship)
• ??? Not mapped: 6+ elements (query parameters, result wrapper)

Key Patterns:

• diagnosisHeader ??? Provenance (authorship tracking)
• diagnosis (body) ??? Condition resource
• diagnosisCode ??? ICD-10-SE or KV?? codes
• diagnosisStatus ??? clinicalStatus + verificationStatus
• Query parameters ??? Search parameters (not stored)

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

Mapping from GetObservations TKB service to FHIR resources. Based on Excel-generated logical model with enhanced field descriptions.

TKB Service: GetObservations v1.0
TKB Domain: clinicalprocess:healthcond:basic v3.1 Logical Model: GetobservationsResponseLM (from FSH-konvertering.xlsx) FHIR Resource: Observation
FHIR Profiles: ObservationVitalSignsInera, ObservationMeasurementInera

Mapping Coverage:

• ??? Mapped to Observation: 20+ elements (code, value, units, reference ranges)
• ??? Mapped to Provenance: 15+ elements (header metadata, authorship)
• ??? Not mapped: 6+ elements (query parameters, result wrapper)

Observation Types:

• Vital Signs: Blood pressure, heart rate, temperature, respiratory rate, SpO2
• Body Measurements: Height, weight, BMI, head circumference, waist circumference
• Clinical Observations: LOINC, NPU, SNOMED CT codes
• Panel/Battery: Composite observations with hasMember

Key Patterns:

• observationHeader ??? Provenance (authorship tracking)
• observation (body) ??? Observation resource
• observationCode ??? LOINC, NPU, or SNOMED CT
• observationValue ??? valueQuantity, valueCodeableConcept, valueString, etc.
• Units ??? UCUM (http://unitsofmeasure.org)
• Query parameters ??? Search parameters (not stored)

Swedish Code Systems:

• NPU codes (Nordic nomenclature for clinical laboratory sciences)
• LOINC codes (preferred for vital signs)
• SNOMED CT SE codes

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 Inera's DocBook format (used in 1177 Inkorg) and FHIR Narrative.div XHTML for formatted text in DocumentReference and Composition