Da Vinci Health Record Exchange (HRex)
1.2.0-cibuild - STU 1.1

Da Vinci Health Record Exchange (HRex), published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 1.2.0-cibuild built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-ehrx/ and changes regularly. See the Directory of published versions

## ValueSet: HRex Consent Policy ValueSet

Official URL: http://hl7.org/fhir/us/davinci-hrex/ValueSet/hrex-consent-policy | Version: 1.2.0-cibuild
Standards status: Draft | Maturity Level: 0 | Computable Name: HRexConsentPolicy
Other Identifiers: OID:2.16.840.1.113883.4.642.40.19.48.1

The set of policy URIs for use in HRex data disclosure consent assertions

References

- HRex Consent Profile

### Logical Definition (CLD)

Generated Narrative: ValueSet hrex-consent-policy

- Include these codes as defined in `urn:ietf:rfc:3986`

  Code | Display
  http://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-consent.html#regular |
  http://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-consent.html#sensitive |

### Expansion

ValueSet

Expansion from tx.fhir.org based on codesystem unknown versionn/a

This value set contains 2 concepts

Code | System | Display (en-US)
http://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-consent.html#regular | urn:ietf:rfc:3986 |
http://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-consent.html#sensitive | urn:ietf:rfc:3986 |

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