Mobile Cross-Enterprise Document Data Element Extraction (mXDE)
1.3.1-current - ci-build International flag

Mobile Cross-Enterprise Document Data Element Extraction (mXDE), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.3.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.mXDE/ and changes regularly. See the Directory of published versions

CapabilityStatement: mXDE Clinical Data Consumer Actor

Official URL: https://profiles.ihe.net/ITI/mXDE/CapabilityStatement/IHE.mXDE.ClinicalDataConsumer Version: 1.3.1-current
Active as of 2023-02-10 Computable Name: IHE_mXDE_DataElementProvenanceConsumer

CapabilityStatement for mXDE Clinical Data Consumer

Raw OpenAPI-Swagger Definition file | Download

Generated Narrative: CapabilityStatement IHE.mXDE.ClinicalDataConsumer

mXDE Clinical Data Consumer Actor

  • Implementation Guide Version: 1.3.1-current
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Supported Patch Formats:
  • Published on: 2023-02-10
  • Published by: IHE IT Infrastructure Technical Committee

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 imports these CapabilityStatementsDocument Consumer (client), http://profiles.ihe.net/ITI/PDQm/CapabilityStatement/IHE.PDQm.client, IHE ITI Patient Identifier Cross-referencing for mobile (PIXm) - Consumer (client), IHE BALP Audit Creator

FHIR RESTful Capabilities

Mode: client

mXDE Clinical Data Consumer Actor

Security

Recommend ATNA, encouraged IHE-IUA or SMART-app-launch

Summary of System-wide Interactions

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 TypeProfileRSUCSearches_include_revincludeOperations
ProvenanceSupported Profiles
  mXDE Provenance
yyyy

Resource Conformance: supported Provenance

Core FHIR Resource
Provenance
Reference Policy
Interaction summary
  • Supports search-type, read, create, update.

Documentation

record