MyHealth@Eu NCPeH API
10.0.0-ci - ci-build 150

MyHealth@Eu NCPeH API - Local Development build (v10.0.0-ci) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Requirements: Actor Definitions

The following artifacts define the types of individuals and/or systems that will interact as part of the use cases covered by this implementation guide.

Requesting NCP

The National Contact Point for eHealth (NCP) node that issues cross-border FHIR requests (search/read/create/update) on behalf of a Requestor, acting as a FHIR client against a Responding NCP.
Responding NCP

The National Contact Point for eHealth (NCP) node that receives and processes cross-border FHIR requests, acting as a FHIR server on behalf of the National Infrastructure.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

CapabilityStatement: myHealth@EU Requesting NCPeH

Describes the requirements that a myHealth@EU NCPeH FHIR client (Requesting NCP) SHALL, SHOULD, or MAY meet to be conformant with this guide. See the RequestingNCP actor definition; the companion server-side requirements are described in CapabilityStatement: myHealth@EU Responding NCPeH, for the RespondingNCP actor.
CapabilityStatement: myHealth@EU Responding NCPeH

Describes the requirements that a myHealth@EU NCPeH FHIR server SHALL, SHOULD, or MAY meet to be conformant with this guide. See the RespondingNCP actor definition; the companion client-side requirements are described in CapabilityStatement: myHealth@EU Requesting NCPeH, for the RequestingNCP actor.

Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

Search by bodySite on DocumentReference

Search DocumentReference resources by body site using the custom DocumentReferenceBodySite extension.
Search by modality on DocumentReference

Search DocumentReference resources by modality using the Modality R5 extension.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

DocumentReference: Minimal

This profile defines the data set returned by the Myhealth@EU Document search service
Patient: Minimal

This profile defines the minimal data set returned by the Myhealth@EU patient 'identification' service

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

eHDSI Document Types

Document Types

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

DocumentReference: example

Example of DocumentReference assoicated to the SimpleChemistryResultReport Laboratory Report (Bundle) example
Patient: example

Patient: example