This page is part of the Electronic Medicinal Product Information (ePI) FHIR Implementation Guide (v1.0.0-ballot: STU1 Ballot 1) based on FHIR v5.0.0-ballot. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/uv/emedicinal-product-info/CapabilityStatement/epi-server | Version: 1.0.0-ballot | |||
Draft as of 2022-10-19 | Responsible: Vulcan Accelerator on behalf of the HL7 PC WG | Computable Name: ePI FHIR Capability Statement (draft 1) |
This section describes a minumum expected capabilities of an ePI FHIR Server which is responsible for providing responses to the queries submitted by the ePI clients. Please refer to the XML or JSON versions of this specification for details on which elements search is to be enabled on. A compliant server SHALL adhere to the requirements listed in this resource, and implement the RESTful behavior according to the FHIR specification.
Raw OpenAPI-Swagger Definition file | Download
This section describes a minumum expected capabilities of an ePI FHIR Server which is responsible for providing responses to the queries submitted by the ePI clients. Please refer to the XML or JSON versions of this specification for details on which elements search is to be enabled on. A compliant server SHALL adhere to the requirements listed in this resource, and implement the RESTful behavior according to the FHIR specification.
Mode | SERVER |
Description | A minumum functionality for ePI. Refer to the FHIR specification for further requirements, and the details in the computable version of this Capabiltiy Statement |
Transaction | y |
System History | y |
System Search | y |