Basic Service Patient Service - Implementation Guide ePA Basic Functionalities v1.3.0
Basisdienst Patient Service - Implementation Guide ePA Basisfunktionalitäten v1.3.0
Summary
This guide specifies how demographic data (name, DOB, etc.) of the insured person should be handled in the electronic health record (ePA). It mandates using FHIR R4 Patient resources to structure data and outlines its usage for payers and other services.
Details
This implementation guide v1.3.0 details the basic functionalities of the Patient Service within the ePA system. The service aims to clearly and uniquely embed demographic data of the insured person (name, date of birth, salutation, etc.) into the electronic health record. This allows payers not only to directly enter this fundamental information into the ePA account but also to promptly report updates for changes in demographic data, such as a change of surname. Technically, this basic functionality is provided via a FHIR R4 Patient resource using a 'FHIR Conditional update.' All FHIR instances are thus linked, direct or indirect, to a Patient resource via a KVNR-based identifier. Furthermore, specific services, such as the ePA Medication Service, internally utilize this Patient resource and add it to search results like the electronic medication list (eML). Implementation requirements mandate that the Patient Service must make all FHIR interfaces available at specified paths. Specifically, a GET call to `/metadata` must return the server's CapabilityStatement, which is crucial for understanding the supported FHIR functionalities. The guide also defines how the payer's client system and the insured person's ePA frontend should utilize specific defined interfaces.
Original content copyright by respective publishers