MyHealth@Eu NCPeH API
9.1.0 - ci-build 150

MyHealth@Eu NCPeH API - Local Development build (v9.1.0) 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.

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 NCPeH Server

Describes the capabilities of the myHealth@EU NCPeH FHIR server for conformance testing and integration.

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

Structures: Extension Definitions

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

DocumentReference BodySite

Indicates the body site or anatomical region related to the document (e.g., left knee, thorax, etc.). This extension is temporarily specified for the DocumentReference resource, pending the adoption of the R5 bodySite CodeableConcept element.

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