The unique id for a particular permission

The activity actor mentioned in a permission rule (permit or deny).

The data period mentioned in a permission rule (permit or deny).

The data resource mentioned in a permission rule (permit or deny).

The element limits mentioned in a permission rule (permit or deny).

Permission resource holds access rules for a given data and access request context.

MyOrg current security roles

Codes identifying rule combining algorithm.

Codes identifying the lifecycle stage of a product.

The codes for Roles in MyOrg

Could possibly use the defined valueSet practitioner-role

Codes identifying the rule combining. See XACML Combining algorithms http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-cos01-en.html

Codes identifying the lifecycle stage of a product.

Consent by the patient to Deny access to the Patient Directory following the Patient Directory policy.

• Consent is by the Patient
• Deny
• policy Basis is the Permission describing patient directory rules

Consent by the patient to allow access to the Patient Directory following the Patient Directory policy.

• Consent is by the Patient
• Permit
• policy Basis is the Permission describing patient directory rules

Consent by the Clinician on behalf of the patient to allow access to the Patient Directory following the Patient Directory policy.

• Consent is by the Practitioner
• Permit
• policy Basis is the Permission describing patient directory rules

Where there is a Permission resource that describes the base policy, then a Consent can point at that Permission rather than a URL alone.

Some would prefer to use the Permission rule encoding, and not the Consent.provision; thus the Consent is used to capture the ceremony, and points at a Permission for the rules.

Dummy MeasureReport example for completeness sake. No actual use of this resource other than an example target that is NOT patient specific.

Dummy Organization example for completeness sake. No actual use of this resource other than an example target

Dummy patient example for completeness sake. No actual use of this resource other than an example target

This patient is the same as ex-patient, with the extension for religious affiliation.

Dummy Practitioner example. This Practitioner has has been de-sensitized from ex-practitioner-sensitive. Note that because the data has been redacted then .meta.security will have tag PROCESSINLINELABEL.

Dummy Practitioner example for completeness sake. No actual use of this resource other than an example target

Dummy Practitioner example. This Practitioner has some phone and address information that is tagged as sensitive location information. Note that because of this the Resource is tagged in .meta.security as having inline tags PROCESSINLINELABEL.

Admin

Dietician

Doctors

Janitor

Registration