Ejemplo de declaración de capacidades - Multi-Language Test IG v0.2.0

IG de Prueba Multilingüe
0.2.0 - International bandera

Multi-Language Test IG, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/FHIR/multi-lang-test-ig/ and changes regularly. See the Directory of published versions

CapabilityStatement: Ejemplo de declaración de capacidades (Experimental)

URL oficial: http://hl7.org/fhir/test/multi-lang/CapabilityStatement/example				Versión: 0.2.0
Standards status: Informative Draft a partir de 2025-08-07 .				Nombre computable: ExampleCapabilityStatement
Utilización: Clinical Focus: positive
Derechos de autor: Copyright © Acme Healthcare y GoodCorp EHR Systems

Ejemplo de declaración de capacidad

Archivo de definición OpenAPI-Swagger sin procesar | Descargar

Spanish

Language: en

Example Capability Statement

Implementation Guide Version: 0.2.0
FHIR Version: 4.0.1
Supported Formats: xml, json
Supported Patch Formats: application/xml-patch+xml, application/json-patch+json
Published on: 2025-08-07 06:51:45+0000
Published by: HL7 International / FHIR Infrastructure

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.

This CapabilityStatement instantiates the CapabilityStatement http://example.org/fhir/CapabilityStatement/pixm-client

SHALL Support the Following Implementation Guides

http://hl7.org/fhir/test/multi-lang/ImplementationGuide/hl7.fhir.test.multi-lang

FHIR RESTful Capabilities

Mode: `server`

Main FHIR endpoint for acem health

Security

Enable CORS: yes

Security services supported: SMART-on-FHIR

See Smart on FHIR documentation

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	C	H-I	H-T	Searches	`_include`	`_revinclude`	Operations
Patient	http://example.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416 Additional supported profiles: `http://example.org/r4/StructureDefinition/00ab9e7a-06c7-4f77-9234-4154ca1e3347`	y	y		y	y	y	y	identifier, general-practitioner	`Organization`	`Person`

Resource Conformance: supported Patient

Base System Profile
http://example.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416

Profile Conformance
SHALL

Reference Policy

Supported Profiles

http://example.org/r4/StructureDefinition/00ab9e7a-06c7-4f77-9234-4154ca1e3347

Interaction summary

Supports read, update, history-instance, create, history-type
vread
Only supported for patient records since 12-Dec 2012

Documentation

This server does not let the clients create identities.

Search Parameters

Conformance	Parameter	Type	Documentation
SHALL	identifier	`token`	Only supports search by institution MRN
SHALL	general-practitioner	`reference`

FHIR Messaging Capabilities

Messaging Capability

Reliable Cache Length
30 Minute(s)

Endpoint(s)

Protocol	Address
MessageTransport mllp: MLLP	mllp:10.1.1.10:9234

Supported Message(s)

Mode	Definition
receiver	`http://example.org/fhir/MessageDefinition/example`