Multi-Language Test IG
0.2.0 - International drapeau

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: Example Capability Statement (Expérimental)

URL officiel: http://hl7.org/fhir/test/multi-lang/CapabilityStatement/example Version: 0.2.0
Standards status: Informative Draft à partir de 2025-08-07 Nom computable: ExampleCapabilityStatement

Utilisation: Clinical Focus: positive

Droit d'auteur/juridique: Copyright © Acme Healthcare and GoodCorp EHR Systems

Example Capability Statement Instance

Fichier de définition d'OpenAPI-Swagger | Télécharger

French

Langue : en

Example Capability Statement

  • Version du guide dimplémentation : {0}
  • Version de FHIR : 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats: application/xml-patch+xml, application/json-patch+json
  • Publié sur : 2025-08-07 06:51:45+0000
  • Publié par : HL7 International / FHIR Infrastructure

Note aux implémenteurs : capacités FHIR

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

DOIT prendre en charge les guides d’implémentation suivants.

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

Résumé

Le tableau récapitulatif liste les ressources faisant partie de cette configuration, et pour chaque ressource, il liste :

  • The relevant profiles (if any)
  • Les interactions supportées par chaque ressource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on T!!les types sont seulement présents si au moins une des ressources les prend en charge.
  • Les paramètres de recherche (SearchParameters) requis, recommandés, optionnels (le cas échéant).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Type de RessourceProfilRV-RSUCH-IH-TRecherches_include_revincludeOpérations
Patienthttp://example.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416
Profils additionnels supportés :
  http://example.org/r4/StructureDefinition/00ab9e7a-06c7-4f77-9234-4154ca1e3347		yyyyyyidentifier, general-practitionerOrganizationPerson

Resource Conformance: supported Patient

Base System Profile
http://example.org/r4/StructureDefinition/7896271d-57f6-4231-89dc-dcc91eab2416
Conformité au Profil
SHALL
Reference Policy

Supported Profiles

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

Résumé des interactions
  • 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.

Paramètres de recherche
ConformitéParamètreTypeDocumentation
SHALLidentifiertoken

Only supports search by institution MRN

SHALLgeneral-practitionerreference
 

FHIR Messaging Capabilities

Messaging Capability

Reliable Cache Length
30 Minute(s)

Endpoint(s)

ProtocolAddress
MessageTransport mllp: MLLPmllp:10.1.1.10:9234

Supported Message(s)

ModeDéfinition
receiverhttp://example.org/fhir/MessageDefinition/example
Documentation

ADT A08 equivalent for external system notifications


FHIR Document Capabilities

ModeDocument Resource ProfileDocumentation
consumerhttp://example.org/base/Profilebc054d23-75e1-4dc6-aca5-838b6b1ac81d/_history/b5fdd9fc-b021-4ea1-911a-721a60663796

Basic rules for all documents in the EHR system