This is the set of resources that conform to both PDex Provider Access Consent Profile (http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-provider-consent) and PDex Provider Access Consent Profile (http://hl7.org/fhir/us/davinci-pdex/StructureDefinition/pdex-provider-consent).
Name Flags Card. Type Description & Constraints Filter: Bindings
Consent C 0..* A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of timeConstraints: ppc-1 , ppc-2 , ppc-3 , ppc-4 , ppc-5 meta Σ 0..1 Meta Metadata about the resource implicitRules ?! Σ 0..1 uri A set of rules under which this content was created language 0..1 code Language of the resource contentBinding: ?? ( preferred ) : A human language. text 0..1 Narrative Text summary of the resource, for human interpretationThis profile does not constrain the narrative in regard to content, language, or traceability to data elements contained 0..* Resource Contained, inline Resources extension 0..* Extension Additional content defined by implementations modifierExtension ?! 0..* Extension Extensions that cannot be ignored identifier Σ 0..* Identifier Identifier for this record (external references)Example General: {"system":"http://acme.org/identifier/local/eCMS","value":"Local eCMS identifier"} status ?! S Σ 1..1 code draft | proposed | active | rejected | inactive | entered-in-errorBinding: ?? ( required ) : Indicates the state of the consent. scope ?! S Σ 1..1 CodeableConcept Which of the four areas this resource covers (extensible)Binding: ?? ( extensible ) : The four anticipated uses for the Consent Resource. category Σ 1..* CodeableConcept Classification of the consent statement - for indexing/retrievalBinding: ?? ( extensible ) : A classification of the type of consents found in a consent statement. patient S Σ 1..1 Reference (US Core Patient Profile(6.1.0) | #sd-us-core-patient-us-core-patient )Who the consent applies to dateTime Σ 0..1 dateTime When this Consent was created or indexed performer S Σ 1..1 Reference (US Core Patient Profile(7.0.0) )Who is agreeing to the policy and rules organization S Σ 1..1 Reference (HRex Organization Profile(1.1.0) )Custodian of the consent source[x] Σ 0..1 Source from which this consent is taken sourceAttachment Attachment Reference (Consent | DocumentReference | Contract | QuestionnaireResponse )policy 0..* BackboneElement Policies covered by this consent extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized authority 0..1 uri Enforcement source for policy uri 0..1 uri Specific policy covered by this consent policyRule Σ 0..1 CodeableConcept Regulation that this consents toBinding: ?? ( extensible ) : Regulatory policy examples. verification Σ 0..* BackboneElement Consent Verified by patient or family extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized verified Σ 1..1 boolean Has been verified verifiedWith 0..1 Reference (Patient | RelatedPerson )Person who verified verificationDate 0..1 dateTime When consent verified provision S Σ 1..1 BackboneElement Constraints to the base Consent.policyRule extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized type S Σ 1..1 code deny | permitBinding: ?? ( required ) : How a rule statement is applied, such as adding additional consent or removing consent. period S Σ 1..1 Period Timeframe for this rule extension 0..* Extension Additional content defined by implementations start S Σ 1..1 dateTime Starting time with inclusive boundary end Σ 0..1 dateTime End time with inclusive boundary, if not ongoing actor 1..* BackboneElement Who|what controlled by this rule (or group, by role) extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized role 1..1 CodeableConcept How the actor is involvedBinding: ?? ( extensible ) : How an actor is involved in the consent considerations. reference 1..1 Reference (Device | Group | CareTeam | Organization | Patient | Practitioner | RelatedPerson | PractitionerRole )Resource for the actor (or group, by role) action Σ 1..1 CodeableConcept Actions controlled by this ruleBinding: ?? ( example ) : Detailed codes for the consent action. securityLabel Σ 0..* Coding Security Labels that define affected resourcesBinding: ?? ( extensible ) : Security Labels from the Healthcare Privacy and Security Classification System. purpose Σ 0..* Coding Context of activities covered by this ruleBinding: ?? ( extensible ) : What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. class Σ 0..* Coding e.g. Resource Type, Profile, CDA, etc.Binding: ?? ( extensible ) : The class (type) of information a consent rule covers. code Σ 0..* CodeableConcept e.g. LOINC or SNOMED CT code, etc. in the contentBinding: ?? ( example ) : If this code is found in an instance, then the exception applies. dataPeriod Σ 0..1 Period Timeframe for data controlled by this rule data Σ 0..* BackboneElement Data controlled by this rule extension 0..* Extension Additional content defined by implementations modifierExtension ?! Σ 0..* Extension Extensions that cannot be ignored even if unrecognized meaning Σ 1..1 code instance | related | dependents | authoredbyBinding: ?? ( required ) : How a resource reference is interpreted when testing consent restrictions. reference Σ 1..1 Reference (Resource )The actual data reference provision 0..* Nested Exception Rules
Consent 
meta 
implicitRules 
contained 
extension 
modifierExtension 
patient 
source[x] 
