| Australian Digital Health Agency Medicare Records FHIR Implementation Guide 2.1.0

Australian Digital Health Agency Medicare Records FHIR Implementation Guide. The current version which supersedes this version is 2.2.0. It is based on FHIR® version 3.0.2. See the Directory of published versions for a list of available versions.

#### StructureDefinition: ADHA Australian Organ Donor Register Consent - Detailed Descriptions

Definitions for the profile.

1. Consent
Definition | A record of a healthcare consumer’s policy choices, which permits or denies identified recipient(s) or recipient role(s) to perform one or more actions within a given policy context, for specific purposes and periods of time.
Control | 0..*
Comments | Broadly, there are 3 key areas of consent for patients: Consent around sharing information (aka Privacy Consent Directive - Authorization to Collect, Use, or Disclose information), consent for specific treatment, or kinds of treatment, and general advance care directives.
2. Consent.id
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Control | 0..1
Type | id
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
3. Consent.meta
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.
Control | 1..1
Type | Meta
4. Consent.meta.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
5. Consent.meta.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Slicing | This element introduces a set of slices on Consent.meta.extension. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ url
6. Consent.meta.versionId
Definition | The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted.
Control | 0..1
Type | id
Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
7. Consent.meta.lastUpdated
Definition | When the resource last changed - e.g. when the version changed.
Control | 0..1
Type | instant
Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant.
8. Consent.meta.profile
Definition | A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url.
Control | 1..*
Type | uri
Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
9. Consent.meta.security
Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
Control | 0..*
Binding | The codes SHALL be taken from All Security Labels; other codes may be used where these codes are not suitable Security Labels from the Healthcare Privacy and Security Classification System
Type | Coding
Comments | The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
10. Consent.meta.tag
Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
Control | 0..*
Binding | For example codes, see Common Tags Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones
Type | Coding
Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
11. Consent.implicitRules
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
Control | 0..1
Type | uri
Is Modifier | true
Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
12. Consent.language
Definition | The base language in which the resource is written.
Control | 0..1
Binding | The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable A human language
Additional Bindings | Purpose
All Languages | Max Binding
Type | code
Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
13. Consent.text
Definition | A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Control | 0..1 This element is affected by the following invariants: dom-1
Type | Narrative
Alternate Names | narrativehtmlxhtmldisplay
Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
14. Consent.contained
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
Control | 0..*
Type | Resource
Alternate Names | inline resourcesanonymous resourcescontained resources
Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
15. Consent.extension
Definition | An Extension
Control | 0..*
Type | Extension
Slicing | This element introduces a set of slices on Consent.extension. The slices are unordered and Open, and can be differentiated using the following discriminators: value @ url
16. Consent.extension:dateInitialRegistration
SliceName | dateInitialRegistration
Definition | The date the individual first registered.
Control | 0..1 This element is affected by the following invariants: ele-1
Type | Extension(DateInitialRegistration) (Extension Type: dateTime)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
17. Consent.extension:donationDecision
SliceName | donationDecision
Definition | The individual's decision about donation.
Control | 1..1 This element is affected by the following invariants: ele-1
Type | Extension(ConsentDonationDecision) (Extension Type: CodeableConcept)
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists())
18. Consent.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
19. Consent.identifier
Definition | Unique identifier for this copy of the Consent Statement.
Note | This is a business identifier, not a resource identifier (see discussion)
Control | 1..1
Type | Identifier
Must Support | true
Comments | This identifier is identifies this copy of the consent. Where this identifier is also used elsewhere as the identifier for a consent record (e.g. a CDA consent document) then the consent details are expected to be the same.
Example | General:<valueIdentifier xmlns="http://hl7.org/fhir"> <system value="urn:ietf:rfc:3986"/> <value value="Local eCMS identifier"/> </valueIdentifier>
20. Consent.status
Definition | Indicates the current state of this consent.
Control | 1..1
Binding | The codes SHALL be taken from ConsentState Indicates the state of the consen
Type | code
Is Modifier | true
Must Support | true
Requirements | The Consent Directive that is pointed to might be in various lifecycle states, e.g., a revoked Consent Directive.
Comments | This element is labeled as a modifier because the status contains the codes rejected and entered-in-error that mark the Consent as not currently valid.
Fixed Value | active
21. Consent.category
Definition | A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.
Control | 1..*
Binding | For example codes, see Consent Category Codes A classification of the type of consents found in a consent statemen
Type | CodeableConcept
Must Support | true
Slicing | This element introduces a set of slices on Consent.category. The slices are unordered and Open, and can be differentiated using the following discriminators: pattern @ $this
22. Consent.category:organDonationConsent
SliceName | organDonationConsent
Definition | A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements.
Control | 1..1
Binding | For example codes, see Consent Category Codes A classification of the type of consents found in a consent statemen
Type | CodeableConcept
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://loinc.org"/> <code value="64300-7"/> </coding> </valueCodeableConcept>
23. Consent.patient
Definition | The patient/healthcare consumer to whom this consent applies.
Control | 1..1
Type | Reference(AUBasePatient))
Must Support | true
Comments | Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person.
24. Consent.period
Definition | Relevant time or time-period when this Consent is applicable.
Control | 0..1
Type | Period
Comments | This can be a subset of the period of the original statement.
Meaning if Missing | all date ranges included
25. Consent.dateTime
Definition | When this Consent was issued / created / indexed.
Control | 1..1
Type | dateTime
Must Support | true
Comments | This is not the time of the original consent, but the time that this statement was made or derived.
26. Consent.consentingParty
Definition | Either the Grantor, which is the entity responsible for granting the rights listed in a Consent Directive or the Grantee, which is the entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions.
Control | 0..*
Type | Reference(RelatedPerson AUBaseOrganisation AUBasePatient AUBasePractitioner))
Alternate Names | consentor
Comments | Commonly, the patient the consent pertains to is the consentor, but particularly for young and old people, it may be some other person - e.g. a legal guardian.
27. Consent.actor
Definition | Who or what is controlled by this consent. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').
Control | 0..*
Type | BackboneElement
Meaning if Missing | There is no specific actor associated with the consent
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
28. Consent.actor.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
29. Consent.actor.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
30. Consent.actor.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
31. Consent.actor.role
Definition | How the individual is involved in the resources content that is described in the consent.
Control | 1..1
Binding | The codes SHALL be taken from SecurityRoleType; other codes may be used where these codes are not suitable How an actor is involved in the consent consideration
Type | CodeableConcept
32. Consent.actor.reference
Definition | The resource that identifies the actor. To identify a actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').
Control | 1..1
Type | Reference(AUBaseDevice Group CareTeam RelatedPerson AUBaseOrganisation AUBasePatient AUBasePractitioner))
33. Consent.action
Definition | Actions controlled by this consent.
Control | 0..*
Binding | For example codes, see Consent Action Codes Detailed codes for the consent action
Type | CodeableConcept
Comments | Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.
Meaning if Missing | all actions
34. Consent.organization
Definition | The organization that manages the consent, and the framework within which it is executed.
Control | 0..1
Type | Reference(AUBaseOrganisation))
Alternate Names | custodian
35. Consent.source[x]
Definition | The source on which this consent statement is based. The source might be a scanned original paper form, or a reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document.
Control | 0..1
Type | Choice of: Attachment, Identifier, Reference(Consent DocumentReference Contract QuestionnaireResponse))
[x] Note | See Choice of Data Types for further information about how to use [x]
Comments | The source can be contained inline (Attachment), referenced directly (Consent), referenced in a consent repository (DocumentReference), or simply by an identifier (Identifier), e.g. a CDA document id.
36. Consent.policy
Definition | The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.
Control | 1..1
Type | BackboneElement
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
37. Consent.policy.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
38. Consent.policy.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
39. Consent.policy.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
40. Consent.policy.authority
Definition | Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives.
Control | 0..1 This element is affected by the following invariants: ppc-1
Type | uri
Must Support | true
Fixed Value | http://australianorgandonorregister.gov.au
41. Consent.policy.uri
Definition | The references to the policies that are included in this consent scope. Policies may be organizational, but are often defined jurisdictionally, or in law.
Control | 1..1 This element is affected by the following invariants: ppc-1
Type | uri
Must Support | true
Comments | This element is for discoverability / documentation, and does not modify or qualify the policy rules.
Fixed Value | http://www.australianorgandonorregister.gov.au/aodr
42. Consent.policyRule
Definition | A referece to the specific computable policy.
Control | 0..1 This element is affected by the following invariants: ppc-1
Type | uri
Requirements | Might be a unique identifier of a policy set in XACML, or other rules engine.
Comments | If the policy reference is not known, the resource cannot be processed. Where the reference is absent, there is no particular policy other than what is expressed directly in the consent resource.
43. Consent.securityLabel
Definition | A set of security labels that define which resources are controlled by this consent. If more than one label is specified, all resources must have all the specified labels.
Control | 0..*
Binding | The codes SHALL be taken from All Security Labels; other codes may be used where these codes are not suitable Security Labels from the Healthcare Privacy and Security Classification System
Type | Coding
Comments | If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. Not all of the security labels make sense for use in this element (may define a narrower value set?).
44. Consent.purpose
Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this consent.
Control | 0..*
Binding | The codes SHALL be taken from PurposeOfUse; other codes may be used where these codes are not suitable What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified label
Type | Coding
Comments | This element is for discoverability / documentation, and does not modify or qualify the policy (e.g. the policy itself describes the purposes for which it applies).
45. Consent.dataPeriod
Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this consent.
Control | 0..1
Type | Period
Comments | This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.
46. Consent.data
Definition | The resources controlled by this consent, if specific resources are referenced.
Control | 0..*
Type | BackboneElement
Meaning if Missing | all data
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
47. Consent.data.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
48. Consent.data.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
49. Consent.data.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
50. Consent.data.meaning
Definition | How the resource reference is interpreted when testing consent restrictions.
Control | 1..1
Binding | The codes SHALL be taken from ConsentDataMeaning How a resource reference is interpreted when testing consent restriction
Type | code
51. Consent.data.reference
Definition | A reference to a specific resource that defines which resources are covered by this consent.
Control | 1..1
Type | Reference(Resource))
52. Consent.except
Definition | Individual's decision about donation of a specific organ or tissue.
Control | 0..*
Type | BackboneElement
Must Support | true
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
53. Consent.except.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
54. Consent.except.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
55. Consent.except.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
56. Consent.except.type
Definition | Action to take - permit or deny - when the exception conditions are met.
Control | 1..1
Binding | The codes SHALL be taken from ConsentExceptType How an exception statement is applied, such as adding additional consent or removing consen
Type | code
Must Support | true
57. Consent.except.period
Definition | The timeframe in this exception is valid.
Control | 0..1
Type | Period
58. Consent.except.actor
Definition | Who or what is controlled by this Exception. Use group to identify a set of actors by some property they share (e.g. 'admitting officers').
Control | 0..*
Type | BackboneElement
Meaning if Missing | There is no specific actor associated with the exception
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
59. Consent.except.actor.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
60. Consent.except.actor.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
61. Consent.except.actor.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
62. Consent.except.actor.role
Definition | How the individual is involved in the resources content that is described in the exception.
Control | 1..1
Binding | The codes SHALL be taken from SecurityRoleType; other codes may be used where these codes are not suitable How an actor is involved in the consent consideration
Type | CodeableConcept
63. Consent.except.actor.reference
Definition | The resource that identifies the actor. To identify a actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers').
Control | 1..1
Type | Reference(AUBaseDevice Group CareTeam RelatedPerson AUBaseOrganisation AUBasePatient AUBasePractitioner))
64. Consent.except.action
Definition | Actions controlled by this Exception.
Control | 1..1
Binding | For example codes, see Consent Action Codes Detailed codes for the consent action
Type | CodeableConcept
Must Support | true
Comments | Note that this is the direct action (not the grounds for the action covered in the purpose element). At present, the only action in the understood and tested scope of this resource is 'read'.
Meaning if Missing | all actions
Pattern Value | <valueCodeableConcept xmlns="http://hl7.org/fhir"> <coding> <system value="http://snomed.info/sct"/> <code value="53958007"/> </coding> </valueCodeableConcept>
65. Consent.except.securityLabel
Definition | A set of security labels that define which resources are controlled by this exception. If more than one label is specified, all resources must have all the specified labels.
Control | 0..*
Binding | The codes SHALL be taken from All Security Labels; other codes may be used where these codes are not suitable Security Labels from the Healthcare Privacy and Security Classification System
Type | Coding
Comments | If the consent specifies a security label of "R" then it applies to all resources that are labeled "R" or lower. E.g. for Confidentiality, it's a high water mark. For other kinds of security labels, subsumption logic applies. Not all of the security labels make sense for use in this element (may define a narrower value set?).
66. Consent.except.purpose
Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this exception.
Control | 0..*
Binding | The codes SHALL be taken from PurposeOfUse; other codes may be used where these codes are not suitable What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified label
Type | Coding
Comments | E.g. if the purpose is 'research', then the operational context must be research, in order for the consent to apply. Not all of the security labels make sense for use in this element (may define a narrower value set?).
67. Consent.except.class
Definition | The class of information covered by this exception. The type can be a FHIR resource type, a profile on a type, or a CDA document, or some other type that indicates what sort of information the consent relates to.
Control | 0..*
Binding | The codes SHALL be taken from Consent Content Class; other codes may be used where these codes are not suitable The class (type) of information a consent rule cover
Type | Coding
Comments | Multiple types are or'ed together. The intention of the contentType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere.
68. Consent.except.code
Definition | If this code is found in an instance, then the exception applies.
Control | 0..*
Binding | For example codes, see Consent Content Codes If this code is found in an instance, then the exception applie
Type | Coding
Comments | Typical use of this is a Document code with class = CDA.
69. Consent.except.dataPeriod
Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this exception.
Control | 0..1
Type | Period
Comments | This has a different sense to the Consent.period - that is when the consent agreement holds. This is the time period of the data that is controlled by the agreement.
70. Consent.except.data
Definition | The body site controlled by this exception.
Control | 1..1
Type | BackboneElement
Must Support | true
Meaning if Missing | all data
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count()))
71. Consent.except.data.id
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Control | 0..1
Type | string
XML Representation | In the XML format, this property is represented as an attribute.
72. Consent.except.data.extension
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Control | 0..*
Type | Extension
Alternate Names | extensionsuser content
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
73. Consent.except.data.modifierExtension
Definition | May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Control | 0..*
Type | Extension
Is Modifier | true
Alternate Names | extensionsuser contentmodifiers
Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
74. Consent.except.data.meaning
Definition | How the resource reference is interpreted when testing consent restrictions.
Control | 1..1
Binding | The codes SHALL be taken from ConsentDataMeaning How a resource reference is interpreted when testing consent restriction
Type | code
Fixed Value | instance
75. Consent.except.data.reference
Definition | A reference to a specific resource that defines which resources are covered by this consent.
Control | 1..1
Type | Reference(ADHABodySiteAODR) : {c})
Must Support | true