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

General Conformance Requirements

General Conformance Requirements

This page defines the general conformance requirements for systems implementing the Inera Core Implementation Guide.

Claiming Conformance

Systems claiming conformance to this Implementation Guide SHALL:

1. Support Swedish Base Profiles
   • Implement the Swedish base profiles for Patient, Practitioner, and Organization
   • Use Swedish national identifiers (personnummer/samordningsnummer, HSA-ID) where applicable
2. Respect Profile Constraints
   • Follow all cardinality constraints derived from TKB logical models
   • Support all mandatory elements as defined in each profile
   • Understand the meaning of Must Support elements (see Must Support)
3. Use Swedish Terminology
   • Use specified Swedish terminology bindings with correct OIDs as documented in profile definitions
   • Support Swedish code systems: ICD-10-SE, NPL, ATC, KV codes, etc.
4. Implement Provenance Tracking
   • Record provenance for all clinical resources to support Patientdatalagen (PDL) compliance
   • Track authorship, timestamps, and organizational responsibility
5. Support RESTful Interactions
   • Implement required FHIR RESTful operations as defined in capability statements
   • Support required search parameters for each resource type

Conformance Levels

Server Conformance

EHR systems acting as FHIR servers SHALL:

• Declare conformance using a CapabilityStatement resource
• Support the SHALL interactions defined in the Capability Statements
• Implement appropriate security measures (see Security)
• Support Swedish patient identification using personnummer/samordningsnummer
• Support HSA-ID for healthcare professional and organization identification

Client Conformance

Systems acting as FHIR clients SHOULD:

• Understand and process all data elements marked as Must Support
• Handle Swedish-specific identifiers and terminology correctly
• Implement appropriate error handling for failed requests

Resource Support

Implementations SHALL support the following core resources with Swedish profiles:

Resource	Profile	Requirement
Patient	SE Base Patient	SHALL
Practitioner	SE Base Practitioner	SHALL
Organization	SE Base Organization	SHALL
AllergyIntolerance	Inera Core AllergyIntolerance	SHOULD
Condition	Inera Core Condition	SHOULD
MedicationStatement	Inera Core MedicationStatement	SHOULD
Observation	Inera Core Observation	SHOULD
Procedure	Inera Core Procedure	SHOULD

PDL Compliance

All implementations SHALL comply with Swedish Patientdatalagen (Patient Data Law) requirements:

• Access Control: Implement appropriate security labels and access controls
• Audit Logging: Maintain comprehensive audit logs of data access
• Provenance: Track the source and responsibility for all clinical data
• Patient Rights: Support patient access to their own data
• Consent Management: Respect patient consent preferences where applicable

Identifier Systems

Implementations SHALL support the following Swedish identifier systems:

Identifier Type	OID	FHIR URI	Usage
Personnummer	1.2.752.129.2.1.3.1	https://terminology.hl7.se/sid/se-personnummer	Swedish national ID
Samordningsnummer	1.2.752.129.2.1.3.3	https://terminology.hl7.se/sid/se-samordningsnummer	Coordination number
HSA-ID (Person)	1.2.752.129.2.1.4.1	https://terminology.hl7.se/sid/se-hsa-personalid	Healthcare professional
HSA-ID (Organization)	1.2.752.129.2.1.4.3	https://terminology.hl7.se/sid/se-hsa-vardenhetsid	Healthcare organization

Validation

Systems SHOULD validate resources against the profiles defined in this IG before exchanging data. Validation tools and test resources are available in the Downloads section.