JohnMoehrke RelatedPerson Consent
0.1.0 - ci-build
JohnMoehrke RelatedPerson Consent
0.1.0 - ci-build
JohnMoehrke RelatedPerson Consent, published by John Moehrke (himself). This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/JohnMoehrke/RelatedPersonConsent/ and changes regularly. See the Directory of published versions
| Official URL: http://johnmoehrke.github.io/RelatedPersonConsent/ValueSet/AuthPurposesVS | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: AuthPurposesVS | ||
ValueSet of the Authorized purposesOfUse types
References
http://terminology.hl7.org/CodeSystem/v3-ActReason| Code | Display | Definition |
| FAMRQT | family requested | To perform one or more operations on information in response to a request by a family member authorized by the patient. |
Expansion based on codesystem ActReason v2.1.1 (CodeSystem)
This value set contains 1 concepts.
| Code | System | Display | Definition |
| FAMRQT | http://terminology.hl7.org/CodeSystem/v3-ActReason | family requested | To perform one or more operations on information in response to a request by a family member authorized by the patient. |
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 |