Mobile access to Health Documents (MHD)
5.0.1-current - ci-build

Mobile access to Health Documents (MHD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 5.0.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.MHD/ and changes regularly. See the Directory of published versions

## ValueSet: participant source types for RESTful create

Official URL: https://profiles.ihe.net/ITI/MHD/ValueSet/DataSources | Version: 5.0.1-current
Active as of 2026-01-13 | Computable Name: DataSources

create agent participant types for user operators that are in REST

References

- Basic AuditEvent for a successful Create not related to a Patient

### Logical Definition (CLD)

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-ParticipationType` version 📦5.0.0

  Code | Display | Definition
  AUT | author (originator) | **Definition:** A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act. **Example:** the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. Examples of such policies might include: * The author and anyone they explicitly delegate may update the report; * All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic; A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party.
  INF | Informant | A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject.
  CST | Custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.).

### Expansion

Expansion performed internally based on codesystem ParticipationType v5.0.0 (CodeSystem)

This value set contains 3 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | AUT | author (originator) | Definition: A party that originates the Act and therefore has responsibility for the information given in the Act and ownership of this Act. Example: the report writer, the person writing the act definition, the guideline author, the placer of an order, the EKG cart (device) creating a report etc. Every Act should have an author. Authorship is regardless of mood always actual authorship. Examples of such policies might include: The author and anyone they explicitly delegate may update the report; All administrators within the same clinic may cancel and reschedule appointments created by other administrators within that clinic; A party that is neither an author nor a party who is extended authorship maintenance rights by policy, may only amend, reverse, override, replace, or follow up in other ways on this Act, whereby the Act remains intact and is linked to another Act authored by that other party. |  |
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | INF | Informant | A source of reported information (e.g., a next of kin who answers questions about the patient's history). For history questions, the patient is logically an informant, yet the informant of history questions is implicitly the subject. |  |
`http://terminology.hl7.org/CodeSystem/v3-ParticipationType` | CST | Custodian | An entity (person, organization or device) that is in charge of maintaining the information of this act (e.g., who maintains the report or the master service catalog item, etc.). |  |

Explanation of the columns that may appear on this page:

Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System | The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code | The code (used as the code in the resource instance)
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition | An explanation of the meaning of the concept
Comments | Additional notes about how to use the code