CH EPR FHIR (R4)
4.0.1 - trial-use
CH EPR FHIR (R4)
4.0.1 - trial-use
This page is part of the CH EPR FHIR (R4) (v4.0.1: DSTU 4) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
| Official URL: http://fhir.ch/ig/ch-epr-fhir/CapabilityStatement/CH.MHD.DocumentConsumer | Version: 4.0.1 | |||
| Active as of 2020-07-08 | Computable Name: CH_MHD_DocumentConsumer | |||
Copyright/Legal: CC0-1.0 |
||||
CapabilityStatement for Actor MHD Document Consumer (client).
Raw OpenAPI-Swagger Definition file | Download
Generated Narrative: CapabilityStatement CH.MHD.DocumentConsumer
application/fhir+xml, application/fhir+jsonNote 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.
clientMHD client requests a list of DocumentReference Resources, matching the supplied set of criteria, from the Document Responder [ITI-67]. MHD client requests a document from the Document Responder [ITI-68].
TLS SHALL be used together with IUA extended access token
search-systeminteraction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include_revinclude| Resource Type | Profile | R | S | U | C | Searches | _include | _revinclude | Operations |
|---|---|---|---|---|---|---|---|---|---|
| DocumentReference | http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ch-mhd-documentreference-comprehensive | y | y | _id, _lastUpdated, author, category, date, event, facility, format, identifier, patient, period, related, security-label, setting, status, type | |||||
| List | http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ch-mhd-submissionset-comprehensive | y | y | _id, _lastupdated, code, creation, date, identifier, subject | |||||
| Binary | y |
read, search-type.| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | _id | token | Logical id of this artifact |
| SHALL | _lastUpdated | date | When the resource version last changed |
| SHALL | author | reference | Who and/or what authored the document |
| SHALL | category | token | Categorization of document |
| SHALL | date | date | When this document reference was created |
| SHALL | event | token | Main clinical acts documented |
| SHALL | facility | token | Kind of facility where patient was seen |
| SHALL | format | token | Format/content rules for the document |
| SHALL | identifier | token | The identifier for this DocumentReference |
| SHALL | patient | reference | Who/what is the subject of the document |
| SHALL | period | date | Time of service that is being documented |
| SHALL | related | reference | Related Resource |
| SHALL | security-label | token | Document security-tags |
| SHALL | setting | token | Additional details about where the content was created (e.g. clinical specialty) |
| SHALL | status | token | current | superseded | entered-in-error |
| SHALL | type | token | Kind of document (LOINC if possible) |
read, search-type.| Conformance | Parameter | Type | Documentation |
|---|---|---|---|
| SHALL | _id | token | Logical id of this artifact |
| SHALL | _lastupdated | date | When the resource version last changed |
| SHALL | code | token | This parameter, of type token, specifies the code.coding value supplied in the List Resource. The value of the code element indicates the List of type SubmissionSet or Folder as indicated. |
| SHALL | creation | date | When this document was created |
| SHALL | date | date | This parameter, of type date, specifies the time when the List was created. |
| SHALL | identifier | token | This parameter, of type token, specifies an identifier for this List. The search results represent the results of a search on List.masterIdentifier and List.identifier. See ITI TF-2: Appendix Z.2 for additional constraints on the use of the token search parameter type. |
| SHALL | subject | reference | This parameter is of type Reference(Patient). The Document Consumer may get this reference through the use of the PDQm or PIXm Profiles, or by some other method. When the patient parameter is used, the Patient reference would need to be accessible to both the Document Consumer and the Document Responder. |