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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
Authorized RelatedPerson |
A RelatedPerson that has been justified and authorized by the Patient.
|
Consent profile for a RelatedPerson relationship |
This defines the constraints on a Consent to indicate that a Patient has agreed and authorizes a Related Person.
|
These define constraints on FHIR data types for systems conforming to this implementation guide.
Extension that points at an authorizing Consent |
Used within a Resource to indicate that the activity enabled by the Resource is authorized by the Consent indicated. For example: Used within a RelatedParty to indicate the Consent the Patient has given authorizing the RelatedParty relationship to exist. |
Retired Extension that points at an authorizing Consent |
Retired: Used within a Resource to indicate that the activity enabled by the Resource is authorized by the Consent indicated. For example: Used within a RelatedParty to indicate the Consent the Patient has given authorizing the RelatedParty relationship to exist. |
These define sets of codes used by systems conforming to this implementation guide.
Authorization purposes for delegation access valueset |
ValueSet of the Authorized purposesOfUse types |
These define new code systems used by systems conforming to this implementation guide.
Consent type that is authorizing a RelatedPerson |
CodeSystem for authorizing Consent types for a RelatedPerson |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
DocumentReference Consent Paperwork example |
DocumentReference example of the paperwork of the Consent |
Example Organization holding the data |
The Organization that holds the data, and enforcing any Consents |
Father - Related Person |
Related Father of the Patient authorized by a Consent |
Patient example |
Patient example for completeness sake. |
Practitioner example doctor |
Practitioner example for the doctor. |
Simple Consent example |
Consent justifying RelatedPerson and authorizing access by that RelatedPerson |