0.1.0 - ci-build
0.1.0 - ci-build
JohnMoehrkeTestConsent, 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/testConsent/ and changes regularly. See the Directory of published versions
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.
| Most Simple Patient Consent |
Consent constrained to just be a patient consent. |
| Simple Consent Privacy with no provision |
Consent constrained minimally to be a patient privacy consent, forbidding any provisions. |
| Simple Consent Privacy with root provision but nothing more |
Consent constrained minimally to be a patient privacy consent, with restriction on one level deep. |
| Simple Consent Privacy with two provisions deep |
Consent constrained minimally to be a patient privacy consent, with restriction of provisions only two levels deep. |
These define new code systems used by systems conforming to this implementation guide.
| One code to identify an activity of profile validating |
one more code |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Consent example with three provisions deep |
This consent is legal Consent, but not to the profiled PrivacyConsent |
| Consent example with two provisions deep |
This consent is legal Consent, and legal profiled PrivacyConsent |
| 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 |
| Patient example |
Patient example for completeness sake. |
| Practitioner example doctor |
Practitioner example for the doctor. |
| Simple Consent example |
Consent justifying authorizing access |