Simple Vulcan ePI Server Capability Statement

Electronic Medicinal Product Information (ePI) FHIR Implementation Guide
1.0.0 - trial-use International flag

Electronic Medicinal Product Information (ePI) FHIR Implementation Guide, published by HL7 International - Biomedical Research & Regulation Work Group. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/emedicinal-product-info/ and changes regularly. See the Directory of published versions

CapabilityStatement: Simple Vulcan ePI Server Capability Statement

Official URL: http://hl7.org/fhir/uv/emedicinal-product-info/CapabilityStatement/simple-vulcan-epi-server				Version: 1.0.0
Active as of 2024-04-07				Computable Name: RestServer

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement simple-vulcan-epi-server

Implementation Guide Version: 1.0.0
FHIR Version: 5.0.0
Supported Formats: application/fhir+xml, xml, application/fhir+json, json, html/json, html/xml
Supported Patch Formats:
Published on: 2024-04-07 09:39:51+0000
Published by: HL7 International - Biomedical Research & Regulation Work Group

Note to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: `server`

Summary of System-wide Interactions

Supports the transactioninteraction.
Supports the history-systeminteraction.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

The relevant profiles (if any)
The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
The required, recommended, and some optional search parameters (if any).
The linked resources enabled for _include
The other resources enabled for _revinclude
The operations on the resource (if any)

Resource Type	Profile	R	V-R	S	U	P	C	D	H-I	H-T	Searches	`_include`	`_revinclude`	Operations
Bundle	http://hl7.org/fhir/StructureDefinition/Bundle Additional supported profiles: Batch bundle Batch response bundle Document bundle History bundle Search Set Bundle Transaction bundle Transaction response bundle Bundle - ePI	y	y	y	y	y	y	y	y	y	_language, identifier, _lastUpdated, _security, type, _filter, _profile, composition, _has, _tag, _source, _id, _content, _text, example-constraint, timestamp	`*`, `Bundle:composition`, `Bundle:example-constraint`, `Bundle:message`	`CodeSystem:derived-from`, `CodeSystem:predecessor`, `Composition:entry`, `Composition:event-reference`, `Composition:related`, `Composition:subject`, `ImplementationGuide:resource`, `List:item`, `List:subject`, `ValueSet:derived-from`, `ValueSet:predecessor`
List	http://hl7.org/fhir/StructureDefinition/List	y	y	y							_language, identifier, item, code, _lastUpdated, source, title, _has, _tag, _source, _id, _text, _content, status	`*`, `List:item`, `List:source`, `List:subject`	`List:item`, `List:subject`

Resource Conformance: supported Bundle

Base System Profile
http://hl7.org/fhir/StructureDefinition/Bundle

Profile Conformance
SHALL

Reference Policy

Supported Profiles

http://hl7.org/fhir/StructureDefinition/batch-bundle
http://hl7.org/fhir/StructureDefinition/batch-response-bundle
http://hl7.org/fhir/StructureDefinition/document-bundle
http://hl7.org/fhir/StructureDefinition/history-bundle
http://hl7.org/fhir/StructureDefinition/search-set-bundle
http://hl7.org/fhir/StructureDefinition/transaction-bundle
http://hl7.org/fhir/StructureDefinition/transaction-response-bundle
http://hl7.org/fhir/uv/emedicinal-product-info/StructureDefinition/Bundle-uv-epi

Interaction summary

Supports search-type, update, vread, read, patch, history-type, history-instance, delete, create.

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	_language	`token`	The language of the resource
SHALL	identifier	`token`	Persistent identifier for the bundle
SHALL	_lastUpdated	`date`	Only return resources which were last updated as specified by the given range
SHALL	_security	`token`	Search for resources which have the given security labels
SHALL	type	`token`	document \| message \| transaction \| transaction-response \| batch \| batch-response \| history \| searchset \| collection \| subscription-notification
SHALL	_filter	`string`	Search the contents of the resource's data using a filter
SHALL	_profile	`uri`	Search for resources which have the given profile
SHALL	composition	`reference`	The first resource in the bundle, if the bundle type is "document" - this is a composition, and this parameter provides access to search its contents
SHALL	_has	`string`	Return resources linked to by the given target
SHALL	_tag	`token`	Search for resources which have the given tag
SHALL	_source	`uri`	Search for resources which have the given source value (Resource.meta.source)
SHALL	_id	`token`	The ID of the resource
SHALL	_content	`string`	Search the contents of the resource's data using a fulltext search
SHALL	_text	`string`	Search the contents of the resource's narrative using a fulltext search
SHALL	example-constraint	`reference`	Search Composition Bundle
SHALL	timestamp	`date`	When the bundle was assembled

Extended Operations

Conformance	Operation	Documentation
SHALL	$validate
SHALL	$meta-delete	Delete tags, profiles, and/or security labels from a resource
SHALL	$meta-add	Add tags, profiles, and/or security labels to a resource
SHALL	$meta	Request a list of tags, profiles, and security labels for a specfic resource instance
SHALL	$expunge

Resource Conformance: supported List

Base System Profile
http://hl7.org/fhir/StructureDefinition/List