Home

Introduction

This implementation guide describes the concepts and information structure related to basic information about persons. It also describes the roles that persons may assume in relation to other persons, for example as a relative or representative. Furthermore, it describes the roles that persons may assume in relation to an organization, for example as an employee, in the role of a patient with a healthcare provider, or as a service user in relation to a social services provider.

This guide is intended as reference material for implementation and other FHIR-related initiatives, rather than as a specification for system integration design.

Target Group

This implementation guide is intended for system owners, architects, system developers, administrators, and system suppliers operating within the health, healthcare, and social care sector.

Background and Context

The data structure of the profiles in this guide is based on identified information needs and requirements with the aim of supporting the realization of the European Health Data Space (EHDS) It is also based on official Swedish requirements for person and personnel data, including regulations and existing national specifications.

Scope and Usage

The FHIR resources used in this specification are Patient, Person, Practitioner, PractitionerRole, RelatedPerson, Organisation. These resources form the foundation for the profiles in this guide and together support a coherent and reusable representation of person-related data within Swedish healthcare and in cross-border scenarios.

The profiles in this guide reuse and build on the R4 Swedish base profiles from HL7 Sweden to ensure consistent profiling and terminology for common Swedish concepts, such as Swedish personal identity numbers and name representations. However, as this guide is part of the Swedish National Digital Infrastructure (NDI), which is based on FHIR R5, it cannot be directly derived from the R4 profiles. In addition, the profiles are aligned with EHDS guidelines. Some constraints used to express EHDS requirements are therefore based on the European base profiles from HL7 Europe. Version 0.1.0-ballot has been used as reference material.

The profiles are intended to be used as base profiles for local, regional and domain-specific implementation guides. They may be further constrained or extended to support specific use-case needs while maintaining alignment with a shared national foundation. Overall, the profiles aim to promote interoperability, consistency and long-term maintainability, while allowing flexibility for different implementation contexts.

Boundaries

This guide does not provide detailed guidelines for how systems should interact with the resources (such as API design, security models or workflow orchestration), nor does it define specific messaging patterns for exchanging them.

Collaboration

External validation has been carried out through dialogue and review with external stakeholders and partner organisations. This external validation has provided valuable feedback on clarity, applicability, and interoperability, and has helped ensure that the specifications meet real-world needs and can be effectively implemented across organisational and sectoral boundaries.