Notice
- Important: This guidance is under active development by NHS England and content may be added or updated on a regular basis.
- This Implementation Guide is currently in Draft and SHOULD NOT be used for development or active implementation without express direction from the NHS England Genomics Unit.
StructureDefinition NHSEngland-Consent-GenomicsPCF
Within Order Management, Consent is only expected to be used for wrapping Record of Discussion resources within the WGS pathway. Consent for testing is implied through submission of a test to the Genomic Order Management service. Consent for Data Access as part of the UGR SHOULD follow guidance provided within Consent guidance page and the IHE PCF Framework.
Only a minimal amount of mandatory information needs to be populated for Order Management recording of RoDs.
The 'per-element' additional guidance provided below only applies to the Order Management use case, for guidance on population of elements for the Unified Genomic Record, see UGR Integration.
| Profile url | FHIR Module | Normative Status |
|---|---|---|
| https://fhir.nhs.uk/StructureDefinition/NHSEngland-Consent-GenomicsPCF | NHS England Genomics | trial-use |
| Canonical_URL | Status | Current_Version | Last_Updated | Description |
|---|---|---|---|---|
| https://fhir.nhs.uk/StructureDefinition/NHSEngland-Consent-GenomicsPCF | active | 0.3.0 | 2026-04-16 | This profile defines the Genomics constraints and extensions on the Privacy and Consent on FHIR FHIR resource Intermediate Consent. |
Tree View
| NHSEngland_Consent_GenomicsPCF (Consent) | C | IntermediateConsent | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| status | Σ ?! | 1..1 | codeBinding |
| scope | Σ ?! | 1..1 | CodeableConceptBindingPattern |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | Σ | 0..* | CodingPattern |
| codingGenomics | Σ | 0..* | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 0..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 0..1 | codeFixed Value |
| display | Σ | 0..1 | stringFixed Value |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| category | Σ | 1..* | CodeableConceptBinding |
| categoryRoD | Σ | 0..1 | CodeableConceptBindingFixed Value |
| categoryUGRDataAccess | Σ | 0..1 | CodeableConceptBindingFixed Value |
| categoryUGRDataSharing | Σ | 0..1 | CodeableConceptBindingFixed Value |
| patient | Σ C | 1..1 | Reference(Patient | NHSEngland_Patient_Genomics) |
| dateTime | Σ | 1..1 | dateTime |
| performer | Σ C | 1..* | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NHSEngland_PractitionerRole_Genomics) |
| organization | Σ C | 1..* | Reference(Organization) |
| organizationUGR | Σ C | 0..1 | Reference(Organization)Fixed Value |
| source[x] | Σ | 1..1 | |
| sourceAttachment | Attachment | ||
| sourceReference | Reference(Consent | Contract | DocumentReference | QuestionnaireResponse) | ||
| policy | 0..* | BackboneElement | |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| authority | C | 0..1 | uri |
| uri | C | 1..1 | uri |
| policyRoD | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| authority | C | 0..1 | uriFixed Value |
| uri | C | 1..1 | uriFixed Value |
| policyUGR | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| authority | C | 0..1 | uri |
| uri | C | 1..1 | uriFixed Value |
| policyRule | Σ C | 0..1 | CodeableConceptBinding |
| verification | Σ | 0..0 | BackboneElement |
| provision | S Σ | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | Σ | 1..1 | codeBinding |
| period | S Σ C | 0..1 | Period |
| actor | S | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 1..1 | CodeableConceptBindingPattern | |
| reference | C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| action | Σ | 0..0 | CodeableConcept |
| securityLabel | Σ | 0..0 | CodingBinding |
| purpose | S Σ | 0..* | CodingBinding |
| class | Σ | 0..0 | CodingBinding |
| code | Σ | 0..0 | CodeableConcept |
| dataPeriod | S Σ C | 0..1 | Period |
| data | S Σ | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBinding |
| reference | Σ C | 1..1 | Reference(Resource) |
| iData | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(Resource | NHSEngland_ServiceRequest_Genomics) |
| rData | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CarePlan | Encounter | EpisodeOfCare) |
| aData | Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| provision | S | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | Σ | 0..1 | codeBinding |
| period | Σ C | 0..1 | Period |
| actor | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 1..1 | CodeableConceptBinding | |
| reference | C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| action | Σ | 0..* | CodeableConcept |
| securityLabel | Σ | 0..* | CodingBinding |
| purpose | S Σ | 0..* | CodingBinding |
| class | Σ | 0..* | CodingBinding |
| code | Σ | 0..* | CodeableConcept |
| dataPeriod | S Σ C | 0..1 | Period |
| data | S Σ | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBinding |
| reference | Σ C | 1..1 | Reference(Resource) |
| iDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(Resource) |
| rDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CarePlan | Encounter | EpisodeOfCare) |
| aDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| provision | 0..0 | see (provision) | |
| provisionUGR | S | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| type | Σ | 1..1 | codeBinding |
| period | Σ C | 0..0 | Period |
| actor | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 1..1 | CodeableConceptBinding | |
| reference | C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| action | Σ | 0..0 | CodeableConcept |
| securityLabel | Σ | 0..0 | CodingBinding |
| purpose | S Σ | 1..* | CodingBinding |
| purposeDirectCare | S Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | codeFixed Value |
| display | Σ | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| purposeResearch | S Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | codeFixed Value |
| display | Σ | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| purposePopulationHealth | S Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | codeFixed Value |
| display | Σ | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| purposeManagementInformation | S Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | codeFixed Value |
| display | Σ | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| purposeFamilyLinkage | S Σ | 0..1 | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ | 1..1 | uriFixed Value |
| version | Σ | 0..1 | string |
| code | Σ | 1..1 | codeFixed Value |
| display | Σ | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| class | Σ | 0..* | CodingBinding |
| code | Σ | 0..0 | CodeableConcept |
| dataPeriod | S Σ C | 0..0 | Period |
| data | S Σ | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBinding |
| reference | Σ C | 1..1 | Reference(Resource) |
| iDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(Resource) |
| rDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CarePlan | Encounter | EpisodeOfCare) |
| aDataP | Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | Σ | 1..1 | codeBindingPattern |
| reference | Σ C | 1..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| provision | 0..0 | see (provision) |
Detailed Descriptions
| Consent | |||
| Short | A healthcare consumer's choices to permit or deny recipients or roles to perform actions for specific purposes and periods of time | ||
| Definition | A record of a healthcare consumer’s 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. | ||
| Cardinality | 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. | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.id | |||
| Short | Logical id of this artifact | ||
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||
| Cardinality | 0..1 | ||
| Type | id | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.meta | |||
| Short | Metadata about the resource | ||
| Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | ||
| Cardinality | 0..1 | ||
| Type | Meta | ||
| Summary | True | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.implicitRules | |||
| Short | A set of rules under which this content was created | ||
| 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. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Modifier | True | ||
| Summary | 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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.language | |||
| Short | Language of the resource content | ||
| Definition | The base language in which the resource is written. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | A human language.
| ||
| 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). | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.text | |||
| Short | Text summary of the resource, for human interpretation | ||
| Definition | A human-readable narrative that contains a summary of the resource and can 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. | ||
| Cardinality | 0..1 | ||
| Type | Narrative | ||
| Alias | narrative, html, xhtml, display | ||
| 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 information is added later. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.contained | |||
| Short | Contained, inline Resources | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | Resource | ||
| Alias | inline resources, anonymous resources, contained 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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. | ||
| Mappings |
| ||
| Consent.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.modifierExtension | |||
| Short | Extensions that cannot be ignored | ||
| 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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Alias | extensions, user content | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.identifier | |||
| Short | Identifier for this record (external references) | ||
| Definition | Unique identifier for this copy of the Consent Statement. | ||
| Cardinality | 0..* | ||
| Type | Identifier | ||
| Summary | True | ||
| Comments | This identifier 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Examples | General{
"system": "urn:ietf:rfc:3986",
"value": "Local eCMS identifier"
} | ||
| Mappings |
| ||
| Consent.status | |||
| Short | draft | proposed | active | rejected | inactive | entered-in-error | ||
| Definition | SHALL be present. Fixed code of 'proposed' where consent discussion has taken place but RoD form has not been provided alongside test order. 'draft' if discussion has not yet taken place and 'active' for completed RoD, regardless of whether the patient has consented to information sharing (responses to specific consent statements SHOULD be recorded in the RoD itself). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | Indicates the state of the consent. | ||
| Modifier | True | ||
| Summary | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope | |||
| Short | Which of the four areas this resource covers (extensible) | ||
| Definition | A selector of the type of consent being presented: ADR, Privacy, Treatment, Research. This list is now extensible. | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | The four anticipated uses for the Consent Resource. | ||
| Modifier | True | ||
| Summary | True | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/consentscope",
"code": "patient-privacy"
}
]
} | ||
| Mappings |
| ||
| Consent.scope.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.scope.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope.coding | |||
| Short | Code defined by a terminology system | ||
| Definition | A reference to a code defined by a terminology system. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | ||
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||
| Slicing | Unordered, Open, by $this(Pattern) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | {
"system": "http://terminology.hl7.org/CodeSystem/consentscope",
"code": "patient-privacy"
} | ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics | |||
| Short | Code defined by a terminology system | ||
| Definition | For WGS RoD this SHALL be fixed to the below code: | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Summary | True | ||
| Requirements | Allows for alternative encodings within a code system, and translations to other code systems. | ||
| Comments | Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/consentscope | ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | patient-privacy | ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | Privacy Consent | ||
| Mappings |
| ||
| Consent.scope.coding:codingGenomics.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.scope.text | |||
| Short | Plain text representation of the concept | ||
| Definition | A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. | ||
| Comments | Very often the text is the same as a displayName of one of the codings. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.category | |||
| Short | Classification of the consent statement - for indexing/retrieval | ||
| Definition | A classification of the type of consents found in the statement. This element supports indexing and retrieval of consent statements. | ||
| Cardinality | 1..* | ||
| Type | CodeableConcept | ||
| Binding | A classification of the type of consents found in a consent statement. | ||
| Summary | True | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Slicing | Unordered, Open, by $this(Pattern) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.category:categoryRoD | |||
| Short | Classification of the consent statement - for indexing/retrieval | ||
| Definition | Fixed to | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A classification of the type of consents found in a consent statement. | ||
| Summary | True | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "RESEARCH",
"display": "research information access"
}
]
} | ||
| Mappings |
| ||
| Consent.category:categoryUGRDataAccess | |||
| Short | Classification of the consent statement - for indexing/retrieval | ||
| Definition | Fixed to | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A classification of the type of consents found in a consent statement. | ||
| Summary | True | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "INFA",
"display": "information access"
}
]
} | ||
| Mappings |
| ||
| Consent.category:categoryUGRDataSharing | |||
| Short | Classification of the consent statement - for indexing/retrieval | ||
| Definition | Fixed to | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | A classification of the type of consents found in a consent statement. | ||
| Summary | True | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
"code": "IDSCL",
"display": "information disclosure"
}
]
} | ||
| Mappings |
| ||
| Consent.patient | |||
| Short | Who the consent applies to | ||
| Definition | SHALL be present. Reference to the associated Patient. This MAY be through a resource reference if the ID on the central service is known (or provided within the transaction bundle) or through NHS number where this is known and has been traced through PDS. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Patient | NHSEngland_Patient_Genomics) | ||
| Summary | True | ||
| Comments | Commonly, the patient the consent pertains to is the author, but for young and old people, it may be some other person. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.dateTime | |||
| Short | When this Consent was created or indexed | ||
| Definition | SHALL be the time the Consent record was created. For UGR Consent, likely auto-populated by the system. | ||
| Cardinality | 1..1 | ||
| Type | dateTime | ||
| Summary | True | ||
| Comments | This is not the time of the original consent, but the time that this statement was made or derived. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.performer | |||
| Short | Who is agreeing to the policy and rules | ||
| Definition | MAY reference a RelatedPerson/Patient or potentially PractitionerRole if consent is being provided via another individual e.g. a proxy, otherwise SHOULD reference the patient themself | ||
| Cardinality | 1..* | ||
| Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NHSEngland_PractitionerRole_Genomics) | ||
| Summary | True | ||
| Alias | 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.organization | |||
| Short | Custodian of the consent | ||
| Definition | The organization that manages the consent, and the framework within which it is executed. | ||
| Cardinality | 1..* | ||
| Type | Reference(Organization) | ||
| Summary | True | ||
| Alias | custodian | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Slicing | Unordered, Open, by $this(Pattern) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.organization:organizationUGR | |||
| Short | Custodian of the consent | ||
| Definition | SHALL be fixed to the ODS code for NHS England (X26) as this is the managing organisation for the UGR consents. | ||
| Cardinality | 0..1 | ||
| Type | Reference(Organization) | ||
| Summary | True | ||
| Alias | custodian | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | {
"identifier": {
"system": "https://fhir.nhs.uk/Id/ods-organization-code",
"value": "X26"
}
} | ||
| Mappings |
| ||
| Consent.source[x] | |||
| Short | Source from which this consent is taken | ||
| Definition | SHALL be present for RoD entities (where the Consent resource provides metadata wrapping around a Record of Discussion Form. The Source element MAY either be: A pointer to the location of the PDF version of the RoD, either hosted by the source/client system Accessed via NRL (via a DocumentReference resource) Embedded within the message payload, base64 encoded (using sourceAttachment) A reference to a QuestionnaireResponse resource (using sourceReference), if this has been collected in a structured format, using the Questionnaire-Genomic Testing RoD template. Not relevant for UGR consent resources as this is generated automatically on creation of a UGR, though IHE PCF requires a reference or attachment. This MAY be a reference to a QuestionnaireResponse representing the patients consent selections, e.g. via the NHS App. | ||
| Cardinality | 1..1 | ||
| Type | Attachment | Reference(Consent | Contract | DocumentReference | QuestionnaireResponse) | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy | |||
| Short | Policies covered by this consent | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Slicing | Unordered, Open, by $this(Pattern) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.policy.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy.authority | |||
| Short | Enforcement source for policy | ||
| Definition | Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy.uri | |||
| Short | Specific policy covered by this consent | ||
| 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. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | This element is for discoverability / documentation and does not modify or qualify the policy rules. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyRoD | |||
| Short | Policies covered by this consent | ||
| 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. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyRoD.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.policy:policyRoD.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyRoD.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyRoD.authority | |||
| Short | Enforcement source for policy | ||
| Definition | Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Fixed Value | https://www.england.nhs.uk | ||
| Mappings |
| ||
| Consent.policy:policyRoD.uri | |||
| Short | Specific policy covered by this consent | ||
| 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. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | This element is for discoverability / documentation and does not modify or qualify the policy rules. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Fixed Value | https://www.england.nhs.uk/publication/nhs-genomic-medicine-service-record-of-discussion-form | ||
| Mappings |
| ||
| Consent.policy:policyUGR | |||
| Short | Policies covered by this consent | ||
| Definition | MAY be used to reference the NHS England Privacy Policy | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyUGR.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.policy:policyUGR.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyUGR.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyUGR.authority | |||
| Short | Enforcement source for policy | ||
| Definition | Entity or Organization having regulatory jurisdiction or accountability for enforcing policies pertaining to Consent Directives. | ||
| Cardinality | 0..1 | ||
| Type | uri | ||
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.policy:policyUGR.uri | |||
| Short | Specific policy covered by this consent | ||
| 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. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Comments | This element is for discoverability / documentation and does not modify or qualify the policy rules. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Fixed Value | https://www.england.nhs.uk/wp-content/uploads/2018/05/nhs-england-privacy-notice-v1.77.pdf | ||
| Mappings |
| ||
| Consent.policyRule | |||
| Short | Regulation that this consents to | ||
| Definition | A reference to the specific base computable regulation or policy. | ||
| Cardinality | 0..1 | ||
| Type | CodeableConcept | ||
| Binding | Regulatory policy examples. | ||
| Summary | True | ||
| Requirements | Might be a unique identifier of a policy set in XACML, or other rules engine. | ||
| Comments | If the policyRule is absent, computable consent would need to be constructed from the elements of the Consent resource. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ppc-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification | |||
| Short | Consent Verified by patient or family | ||
| Definition | Whether a treatment instruction (e.g. artificial respiration yes or no) was verified with the patient, his/her family or another authorized person. | ||
| Cardinality | 0..0 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.verification.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification.verified | |||
| Short | Has been verified | ||
| Definition | Has the instruction been verified. | ||
| Cardinality | 1..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification.verifiedWith | |||
| Short | Person who verified | ||
| Definition | Who verified the instruction (Patient, Relative or other Authorized Person). | ||
| Cardinality | 0..1 | ||
| Type | Reference(Patient | RelatedPerson) | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.verification.verificationDate | |||
| Short | When consent verified | ||
| Definition | Date verification was collected. | ||
| Cardinality | 0..1 | ||
| Type | dateTime | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision | |||
| Short | Constraints to the base Consent.policyRule | ||
| Definition | Within Order Management used to reference the ServiceRequest the Consent applies to. SHALL be present where the consent only applies to a specific test. In the context of the UGR, the top level | ||
| Cardinality | 1..1 | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.type | |||
| Short | deny | permit | ||
| Definition | Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a rule statement is applied, such as adding additional consent or removing consent. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.period | |||
| Short | Timeframe for this rule | ||
| Definition | The timeframe in this rule is valid. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.actor | |||
| Short | Who|what controlled by this rule (or group, by role) | ||
| Definition | Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Meaning when missing | There is no specific actor associated with the exception | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.actor.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.actor.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.actor.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.actor.role | |||
| Short | How the actor is involved | ||
| Definition | How the individual is involved in the resources content that is described in the exception. | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | How an actor is involved in the consent considerations. | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
"code": "IRCP"
}
]
} | ||
| Mappings |
| ||
| Consent.provision.actor.reference | |||
| Short | Resource for the actor (or group, by role) | ||
| Definition | The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers'). | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.action | |||
| Short | Actions controlled by this rule | ||
| Definition | Actions controlled by this Rule. | ||
| Cardinality | 0..0 | ||
| Type | CodeableConcept | ||
| Binding | Detailed codes for the consent action. | ||
| Summary | 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 when missing | all actions | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.securityLabel | |||
| Short | Security Labels that define affected resources | ||
| Definition | A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. | ||
| Cardinality | 0..0 | ||
| Type | Coding | ||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||
| Summary | True | ||
| 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. When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.purpose | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.class | |||
| Short | e.g. Resource Type, Profile, CDA, etc. | ||
| Definition | The class of information covered by this rule. 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. | ||
| Cardinality | 0..0 | ||
| Type | Coding | ||
| Binding | The class (type) of information a consent rule covers. | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.code | |||
| Short | e.g. LOINC or SNOMED CT code, etc. in the content | ||
| Definition | If this code is found in an instance, then the rule applies. | ||
| Cardinality | 0..0 | ||
| Type | CodeableConcept | ||
| Binding | If this code is found in an instance, then the exception applies. | ||
| Summary | True | ||
| Comments | Typical use of this is a Document code with class = CDA. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.dataPeriod | |||
| Short | Timeframe for data controlled by this rule | ||
| Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Must Support | True | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Slicing | Unordered, Closed, by meaning(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.data.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:iData | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:iData.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.data:iData.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:iData.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:iData.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | instance | ||
| Mappings |
| ||
| Consent.provision.data:iData.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource | NHSEngland_ServiceRequest_Genomics) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:rData | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:rData.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.data:rData.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:rData.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:rData.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | related | ||
| Mappings |
| ||
| Consent.provision.data:rData.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CarePlan | Encounter | EpisodeOfCare) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:aData | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:aData.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.data:aData.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:aData.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.data:aData.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | authoredby | ||
| Mappings |
| ||
| Consent.provision.data:aData.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision | |||
| Short | Nested Exception Rules | ||
| Definition | Rules which provide exceptions to the base rule or subrules. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Slicing | Unordered, Open, by $this(Pattern) | ||
| Consent.provision.provision.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.type | |||
| Short | deny | permit | ||
| Definition | Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules. | ||
| Cardinality | 0..1 | ||
| Type | code | ||
| Binding | How a rule statement is applied, such as adding additional consent or removing consent. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.period | |||
| Short | Timeframe for this rule | ||
| Definition | The timeframe in this rule is valid. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Summary | True | ||
| Comments | A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.actor | |||
| Short | Who|what controlled by this rule (or group, by role) | ||
| Definition | Who or what is controlled by this rule. Use group to identify a set of actors by some property they share (e.g. 'admitting officers'). | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Meaning when missing | There is no specific actor associated with the exception | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.actor.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.actor.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.actor.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.actor.role | |||
| Short | How the actor is involved | ||
| Definition | How the individual is involved in the resources content that is described in the exception. | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | How an actor is involved in the consent considerations. | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.actor.reference | |||
| Short | Resource for the actor (or group, by role) | ||
| Definition | The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers'). | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.action | |||
| Short | Actions controlled by this rule | ||
| Definition | Actions controlled by this Rule. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | Detailed codes for the consent action. | ||
| Summary | 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 when missing | all actions | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.securityLabel | |||
| Short | Security Labels that define affected resources | ||
| Definition | A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||
| Summary | True | ||
| 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. When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.purpose | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.class | |||
| Short | e.g. Resource Type, Profile, CDA, etc. | ||
| Definition | The class of information covered by this rule. 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. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | The class (type) of information a consent rule covers. | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.code | |||
| Short | e.g. LOINC or SNOMED CT code, etc. in the content | ||
| Definition | If this code is found in an instance, then the rule applies. | ||
| Cardinality | 0..* | ||
| Type | CodeableConcept | ||
| Binding | If this code is found in an instance, then the exception applies. | ||
| Summary | True | ||
| Comments | Typical use of this is a Document code with class = CDA. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.dataPeriod | |||
| Short | Timeframe for data controlled by this rule | ||
| Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Period | ||
| Must Support | True | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Slicing | Unordered, Closed, by meaning(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.data.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | instance | ||
| Mappings |
| ||
| Consent.provision.provision.data:iDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | related | ||
| Mappings |
| ||
| Consent.provision.provision.data:rDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CarePlan | Encounter | EpisodeOfCare) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | authoredby | ||
| Mappings |
| ||
| Consent.provision.provision.data:aDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision.provision | |||
| Short | Nested Exception Rules | ||
| Definition | Rules which provide exceptions to the base rule or subrules. | ||
| Cardinality | 0..0 | ||
| Type | see (provision) | ||
| Consent.provision.provision:provisionUGR | |||
| Short | Nested Exception Rules | ||
| Definition | Rules which provide exceptions to the base rule or subrules. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Consent.provision.provision:provisionUGR.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.type | |||
| Short | deny | permit | ||
| Definition | Action to take - permit or deny - when the rule conditions are met. Not permitted in root rule, required in all nested rules. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a rule statement is applied, such as adding additional consent or removing consent. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.period | |||
| Short | Timeframe for this rule | ||
| Definition | The timeframe in this rule is valid. | ||
| Cardinality | 0..0 | ||
| Type | Period | ||
| Summary | True | ||
| Comments | A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor | |||
| Short | Who|what controlled by this rule (or group, by role) | ||
| Definition | MAY be used to specify a class of individuals included within the consent statement, e.g. access for direct care by healthcare professionals, or for individuals, e.g. access to patient proxy. | ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Meaning when missing | There is no specific actor associated with the exception | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor.role | |||
| Short | How the actor is involved | ||
| Definition | How the individual is involved in the resources content that is described in the exception. | ||
| Cardinality | 1..1 | ||
| Type | CodeableConcept | ||
| Binding | How an actor is involved in the consent considerations. | ||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.actor.reference | |||
| Short | Resource for the actor (or group, by role) | ||
| Definition | The resource that identifies the actor. To identify actors by type, use group to identify a set of actors by some property they share (e.g. 'admitting officers'). | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.action | |||
| Short | Actions controlled by this rule | ||
| Definition | Actions controlled by this Rule. | ||
| Cardinality | 0..0 | ||
| Type | CodeableConcept | ||
| Binding | Detailed codes for the consent action. | ||
| Summary | 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 when missing | all actions | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.securityLabel | |||
| Short | Security Labels that define affected resources | ||
| Definition | A security label, comprised of 0..* security label fields (Privacy tags), which define which resources are controlled by this exception. | ||
| Cardinality | 0..0 | ||
| Type | Coding | ||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||
| Summary | True | ||
| 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. When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose | |||
| Short | Context of activities covered by this rule | ||
| Definition | SHALL be used for encoding the four lenses of data access | ||
| Cardinality | 1..* | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Slicing | Unordered, Open, by code(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/v3-ActReason | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | TREAT | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/v3-ActReason | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | HRESCH | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/v3-ActReason | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | POPHLTH | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/v3-ActReason | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | HOPERAT | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage | |||
| Short | Context of activities covered by this rule | ||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this rule. | ||
| Cardinality | 0..1 | ||
| Type | Coding | ||
| Binding | What purposes of use are controlled by this exception. If more than one label is specified, operations must have all the specified labels. | ||
| Must Support | True | ||
| Summary | True | ||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.system | |||
| Short | Identity of the terminology system | ||
| Definition | The identification of the code system that defines the meaning of the symbol in the code. | ||
| Cardinality | 1..1 | ||
| Type | uri | ||
| Summary | True | ||
| Requirements | Need to be unambiguous about the source of the definition of the symbol. | ||
| Comments | The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | http://terminology.hl7.org/CodeSystem/v3-ActReason | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.version | |||
| Short | Version of the system - if relevant | ||
| Definition | The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Comments | Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.code | |||
| Short | Symbol in syntax defined by the system | ||
| Definition | A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Summary | True | ||
| Requirements | Need to refer to a particular code in the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Fixed Value | FAMRQT | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.display | |||
| Short | Representation defined by the system | ||
| Definition | A representation of the meaning of the code in the system, following the rules of the system. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Summary | True | ||
| Requirements | Need to be able to carry a human-readable meaning of the code for readers that do not know the system. | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.userSelected | |||
| Short | If this coding was chosen directly by the user | ||
| Definition | Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). | ||
| Cardinality | 0..1 | ||
| Type | boolean | ||
| Summary | True | ||
| Requirements | This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. | ||
| Comments | Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.class | |||
| Short | e.g. Resource Type, Profile, CDA, etc. | ||
| Definition | MAY be used to indicate the classes of data the provision applies to, where whole classes of data, e.g. DiagnosticReports, are consented to, rather than specific instances. | ||
| Cardinality | 0..* | ||
| Type | Coding | ||
| Binding | The class (type) of information a consent rule covers. | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.code | |||
| Short | e.g. LOINC or SNOMED CT code, etc. in the content | ||
| Definition | If this code is found in an instance, then the rule applies. | ||
| Cardinality | 0..0 | ||
| Type | CodeableConcept | ||
| Binding | If this code is found in an instance, then the exception applies. | ||
| Summary | True | ||
| Comments | Typical use of this is a Document code with class = CDA. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.dataPeriod | |||
| Short | Timeframe for data controlled by this rule | ||
| Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this rule. | ||
| Cardinality | 0..0 | ||
| Type | Period | ||
| Must Support | True | ||
| Summary | True | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data | |||
| Short | Data controlled by this rule | ||
| Definition | SHOULD be used where the consent applies to specific instances of data, such as a single report or sequence.
| ||
| Cardinality | 0..* | ||
| Type | BackboneElement | ||
| Must Support | True | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Slicing | Unordered, Closed, by meaning(Value) | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | instance | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:iDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(Resource) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | related | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:rDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CarePlan | Encounter | EpisodeOfCare) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP | |||
| Short | Data controlled by this rule | ||
| Definition | The resources controlled by this rule if specific resources are referenced. | ||
| Cardinality | 0..1 | ||
| Type | BackboneElement | ||
| Summary | True | ||
| Meaning when missing | all data | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP.id | |||
| Short | Unique id for inter-element referencing | ||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||
| Cardinality | 0..1 | ||
| Type | string | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP.extension | |||
| Short | Additional content defined by implementations | ||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Alias | extensions, user 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 | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP.modifierExtension | |||
| Short | Extensions that cannot be ignored even if unrecognized | ||
| 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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||
| Cardinality | 0..* | ||
| Type | Extension | ||
| Modifier | True | ||
| Summary | True | ||
| Alias | extensions, user content, modifiers | ||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||
| 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. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP.meaning | |||
| Short | instance | related | dependents | authoredby | ||
| Definition | How the resource reference is interpreted when testing consent restrictions. | ||
| Cardinality | 1..1 | ||
| Type | code | ||
| Binding | How a resource reference is interpreted when testing consent restrictions. | ||
| Summary | True | ||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Pattern | authoredby | ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.data:aDataP.reference | |||
| Short | The actual data reference | ||
| Definition | A reference to a specific resource that defines which resources are covered by this consent. | ||
| Cardinality | 1..1 | ||
| Type | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||
| Summary | True | ||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||
| Constraints |
| ||
| Mappings |
| ||
| Consent.provision.provision:provisionUGR.provision | |||
| Short | Nested Exception Rules | ||
| Definition | Rules which provide exceptions to the base rule or subrules. | ||
| Cardinality | 0..0 | ||
| Type | see (provision) | ||
Table View
| Consent | 0..* | |
| Consent.id | id | 0..1 |
| Consent.meta | Meta | 0..1 |
| Consent.implicitRules | uri | 0..1 |
| Consent.language | code | 0..1 |
| Consent.text | Narrative | 0..1 |
| Consent.contained | Resource | 0..* |
| Consent.extension | Extension | 0..* |
| Consent.modifierExtension | Extension | 0..* |
| Consent.identifier | Identifier | 0..* |
| Consent.status | code | 1..1 |
| Consent.scope | CodeableConcept | 1..1 |
| Consent.scope.id | string | 0..1 |
| Consent.scope.extension | Extension | 0..* |
| Consent.scope.coding | Coding | 0..* |
| Consent.scope.coding:codingGenomics | Coding | 0..* |
| Consent.scope.coding:codingGenomics.id | string | 0..1 |
| Consent.scope.coding:codingGenomics.extension | Extension | 0..* |
| Consent.scope.coding:codingGenomics.system | uri | 0..1 |
| Consent.scope.coding:codingGenomics.version | string | 0..1 |
| Consent.scope.coding:codingGenomics.code | code | 0..1 |
| Consent.scope.coding:codingGenomics.display | string | 0..1 |
| Consent.scope.coding:codingGenomics.userSelected | boolean | 0..1 |
| Consent.scope.text | string | 0..1 |
| Consent.category | CodeableConcept | 1..* |
| Consent.category:categoryRoD | CodeableConcept | 0..1 |
| Consent.category:categoryUGRDataAccess | CodeableConcept | 0..1 |
| Consent.category:categoryUGRDataSharing | CodeableConcept | 0..1 |
| Consent.patient | Reference(Patient | NHSEngland_Patient_Genomics) | 1..1 |
| Consent.dateTime | dateTime | 1..1 |
| Consent.performer | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson | NHSEngland_PractitionerRole_Genomics) | 1..* |
| Consent.organization | Reference(Organization) | 1..* |
| Consent.organization:organizationUGR | Reference(Organization) | 0..1 |
| Consent.source[x] | Attachment | Reference(Consent | Contract | DocumentReference | QuestionnaireResponse) | 1..1 |
| Consent.policy | BackboneElement | 0..* |
| Consent.policy.id | string | 0..1 |
| Consent.policy.extension | Extension | 0..* |
| Consent.policy.modifierExtension | Extension | 0..* |
| Consent.policy.authority | uri | 0..1 |
| Consent.policy.uri | uri | 1..1 |
| Consent.policy:policyRoD | BackboneElement | 0..* |
| Consent.policy:policyRoD.id | string | 0..1 |
| Consent.policy:policyRoD.extension | Extension | 0..* |
| Consent.policy:policyRoD.modifierExtension | Extension | 0..* |
| Consent.policy:policyRoD.authority | uri | 0..1 |
| Consent.policy:policyRoD.uri | uri | 1..1 |
| Consent.policy:policyUGR | BackboneElement | 0..* |
| Consent.policy:policyUGR.id | string | 0..1 |
| Consent.policy:policyUGR.extension | Extension | 0..* |
| Consent.policy:policyUGR.modifierExtension | Extension | 0..* |
| Consent.policy:policyUGR.authority | uri | 0..1 |
| Consent.policy:policyUGR.uri | uri | 1..1 |
| Consent.policyRule | CodeableConcept | 0..1 |
| Consent.verification | BackboneElement | 0..0 |
| Consent.verification.id | string | 0..1 |
| Consent.verification.extension | Extension | 0..* |
| Consent.verification.modifierExtension | Extension | 0..* |
| Consent.verification.verified | boolean | 1..1 |
| Consent.verification.verifiedWith | Reference(Patient | RelatedPerson) | 0..1 |
| Consent.verification.verificationDate | dateTime | 0..1 |
| Consent.provision | BackboneElement | 1..1 |
| Consent.provision.id | string | 0..1 |
| Consent.provision.extension | Extension | 0..* |
| Consent.provision.modifierExtension | Extension | 0..* |
| Consent.provision.type | code | 1..1 |
| Consent.provision.period | Period | 0..1 |
| Consent.provision.actor | BackboneElement | 0..* |
| Consent.provision.actor.id | string | 0..1 |
| Consent.provision.actor.extension | Extension | 0..* |
| Consent.provision.actor.modifierExtension | Extension | 0..* |
| Consent.provision.actor.role | CodeableConcept | 1..1 |
| Consent.provision.actor.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.action | CodeableConcept | 0..0 |
| Consent.provision.securityLabel | Coding | 0..0 |
| Consent.provision.purpose | Coding | 0..* |
| Consent.provision.class | Coding | 0..0 |
| Consent.provision.code | CodeableConcept | 0..0 |
| Consent.provision.dataPeriod | Period | 0..1 |
| Consent.provision.data | BackboneElement | 0..* |
| Consent.provision.data.id | string | 0..1 |
| Consent.provision.data.extension | Extension | 0..* |
| Consent.provision.data.modifierExtension | Extension | 0..* |
| Consent.provision.data.meaning | code | 1..1 |
| Consent.provision.data.reference | Reference(Resource) | 1..1 |
| Consent.provision.data:iData | BackboneElement | 0..* |
| Consent.provision.data:iData.id | string | 0..1 |
| Consent.provision.data:iData.extension | Extension | 0..* |
| Consent.provision.data:iData.modifierExtension | Extension | 0..* |
| Consent.provision.data:iData.meaning | code | 1..1 |
| Consent.provision.data:iData.reference | Reference(Resource | NHSEngland_ServiceRequest_Genomics) | 1..1 |
| Consent.provision.data:rData | BackboneElement | 0..* |
| Consent.provision.data:rData.id | string | 0..1 |
| Consent.provision.data:rData.extension | Extension | 0..* |
| Consent.provision.data:rData.modifierExtension | Extension | 0..* |
| Consent.provision.data:rData.meaning | code | 1..1 |
| Consent.provision.data:rData.reference | Reference(CarePlan | Encounter | EpisodeOfCare) | 1..1 |
| Consent.provision.data:aData | BackboneElement | 0..* |
| Consent.provision.data:aData.id | string | 0..1 |
| Consent.provision.data:aData.extension | Extension | 0..* |
| Consent.provision.data:aData.modifierExtension | Extension | 0..* |
| Consent.provision.data:aData.meaning | code | 1..1 |
| Consent.provision.data:aData.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.provision | BackboneElement | 0..* |
| Consent.provision.provision.id | string | 0..1 |
| Consent.provision.provision.extension | Extension | 0..* |
| Consent.provision.provision.modifierExtension | Extension | 0..* |
| Consent.provision.provision.type | code | 0..1 |
| Consent.provision.provision.period | Period | 0..1 |
| Consent.provision.provision.actor | BackboneElement | 0..* |
| Consent.provision.provision.actor.id | string | 0..1 |
| Consent.provision.provision.actor.extension | Extension | 0..* |
| Consent.provision.provision.actor.modifierExtension | Extension | 0..* |
| Consent.provision.provision.actor.role | CodeableConcept | 1..1 |
| Consent.provision.provision.actor.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.provision.action | CodeableConcept | 0..* |
| Consent.provision.provision.securityLabel | Coding | 0..* |
| Consent.provision.provision.purpose | Coding | 0..* |
| Consent.provision.provision.class | Coding | 0..* |
| Consent.provision.provision.code | CodeableConcept | 0..* |
| Consent.provision.provision.dataPeriod | Period | 0..1 |
| Consent.provision.provision.data | BackboneElement | 0..* |
| Consent.provision.provision.data.id | string | 0..1 |
| Consent.provision.provision.data.extension | Extension | 0..* |
| Consent.provision.provision.data.modifierExtension | Extension | 0..* |
| Consent.provision.provision.data.meaning | code | 1..1 |
| Consent.provision.provision.data.reference | Reference(Resource) | 1..1 |
| Consent.provision.provision.data:iDataP | BackboneElement | 0..1 |
| Consent.provision.provision.data:iDataP.id | string | 0..1 |
| Consent.provision.provision.data:iDataP.extension | Extension | 0..* |
| Consent.provision.provision.data:iDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision.data:iDataP.meaning | code | 1..1 |
| Consent.provision.provision.data:iDataP.reference | Reference(Resource) | 1..1 |
| Consent.provision.provision.data:rDataP | BackboneElement | 0..1 |
| Consent.provision.provision.data:rDataP.id | string | 0..1 |
| Consent.provision.provision.data:rDataP.extension | Extension | 0..* |
| Consent.provision.provision.data:rDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision.data:rDataP.meaning | code | 1..1 |
| Consent.provision.provision.data:rDataP.reference | Reference(CarePlan | Encounter | EpisodeOfCare) | 1..1 |
| Consent.provision.provision.data:aDataP | BackboneElement | 0..1 |
| Consent.provision.provision.data:aDataP.id | string | 0..1 |
| Consent.provision.provision.data:aDataP.extension | Extension | 0..* |
| Consent.provision.provision.data:aDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision.data:aDataP.meaning | code | 1..1 |
| Consent.provision.provision.data:aDataP.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.provision.provision | 0..0 | |
| Consent.provision.provision:provisionUGR | BackboneElement | 0..* |
| Consent.provision.provision:provisionUGR.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.type | code | 1..1 |
| Consent.provision.provision:provisionUGR.period | Period | 0..0 |
| Consent.provision.provision:provisionUGR.actor | BackboneElement | 0..* |
| Consent.provision.provision:provisionUGR.actor.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.actor.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.actor.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.actor.role | CodeableConcept | 1..1 |
| Consent.provision.provision:provisionUGR.actor.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.provision:provisionUGR.action | CodeableConcept | 0..0 |
| Consent.provision.provision:provisionUGR.securityLabel | Coding | 0..0 |
| Consent.provision.provision:provisionUGR.purpose | Coding | 1..* |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare | Coding | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.system | uri | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.version | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.code | code | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.display | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeDirectCare.userSelected | boolean | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch | Coding | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.system | uri | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.version | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.code | code | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.display | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeResearch.userSelected | boolean | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth | Coding | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.system | uri | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.version | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.code | code | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.display | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposePopulationHealth.userSelected | boolean | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation | Coding | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.system | uri | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.version | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.code | code | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.display | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeManagementInformation.userSelected | boolean | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage | Coding | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.system | uri | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.version | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.code | code | 1..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.display | string | 0..1 |
| Consent.provision.provision:provisionUGR.purpose:purposeFamilyLinkage.userSelected | boolean | 0..1 |
| Consent.provision.provision:provisionUGR.class | Coding | 0..* |
| Consent.provision.provision:provisionUGR.code | CodeableConcept | 0..0 |
| Consent.provision.provision:provisionUGR.dataPeriod | Period | 0..0 |
| Consent.provision.provision:provisionUGR.data | BackboneElement | 0..* |
| Consent.provision.provision:provisionUGR.data.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.data.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data.meaning | code | 1..1 |
| Consent.provision.provision:provisionUGR.data.reference | Reference(Resource) | 1..1 |
| Consent.provision.provision:provisionUGR.data:iDataP | BackboneElement | 0..1 |
| Consent.provision.provision:provisionUGR.data:iDataP.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.data:iDataP.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:iDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:iDataP.meaning | code | 1..1 |
| Consent.provision.provision:provisionUGR.data:iDataP.reference | Reference(Resource) | 1..1 |
| Consent.provision.provision:provisionUGR.data:rDataP | BackboneElement | 0..1 |
| Consent.provision.provision:provisionUGR.data:rDataP.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.data:rDataP.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:rDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:rDataP.meaning | code | 1..1 |
| Consent.provision.provision:provisionUGR.data:rDataP.reference | Reference(CarePlan | Encounter | EpisodeOfCare) | 1..1 |
| Consent.provision.provision:provisionUGR.data:aDataP | BackboneElement | 0..1 |
| Consent.provision.provision:provisionUGR.data:aDataP.id | string | 0..1 |
| Consent.provision.provision:provisionUGR.data:aDataP.extension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:aDataP.modifierExtension | Extension | 0..* |
| Consent.provision.provision:provisionUGR.data:aDataP.meaning | code | 1..1 |
| Consent.provision.provision:provisionUGR.data:aDataP.reference | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | 1..1 |
| Consent.provision.provision:provisionUGR.provision | 0..0 |
XML View
JSON View
- Consent-RoD-PheobeSmitham-Example
- Consent-RoD-PheobeSmithamFather-Example
- Consent-RoD-PheobeSmithamMother-Example
- Consent-RoD-PheobeSmithamYoungPersonAssentForm-Example
- Consent-RoDYoungPersonAssentFormAvailable-Example
- Consent-RoDAvailable-Example
- Consent-RoDToFollow-Example
- Consent-RoD-PheobeSmithamAttachmentURL-Example
- Consent-RoD-PheobeSmithamAttachmentData-Example
| FHIR | MDS | HL7v2 |
|---|---|---|
| Consent.sourceAttachment | RoD - Record of discussion form - copy attached | CON-19 (for OML, included in RoD, referenced from NTE-3) |
| Consent.status | RoD - Patient conversation taken place, ROD form to follow | Inferred through CON-19 value (for OML, included in RoD, referenced from NTE-3) |
Additional Guidance
status
SHALL be present. Fixed code of 'proposed' where consent discussion has taken place but RoD form has not been provided alongside test order. 'draft' if discussion has not yet taken place and 'active' for completed RoD, regardless of whether the patient has consented to information sharing (responses to specific consent statements SHOULD be recorded in the RoD itself)."status": "proposed",
scope
For WGS RoD this SHALL be fixed to the below code:"scope": { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/consentscope", "code": "patient-privacy", "display": "Privacy Consent" } ] },
category
For WGS RoD this SHALL be fixed to the below code:"category": [ { "coding": [ { "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode", "code": "RESEARCH", "display": "research information access" } ] } ],
patient
SHALL be present. Reference to the associated Patient. This MAY be through a resource reference if the ID on the central service is known (or provided within the transaction bundle) or through NHS number where this is known and has been traced through PDS."subject": { "reference": "Patient/Patient-MeirLieberman-Example", "identifier": { "system": "https://fhir.nhs.uk/Id/nhs-number", "value": "9449307873" } },
source[x]
SHALL be present for RoD entities (where the Consent resource provides metadata wrapping around a [Record of Discussion Form](https://www.england.nhs.uk/publication/nhs-genomic-medicine-service-record-of-discussion-form/). The Source element MAY either be:- A pointer to the location of the PDF version of the RoD, either hosted by the source/client system
- Accessed via NRL (via a DocumentReference resource)
- Embedded within the message payload, base64 encoded (using sourceAttachment)
- A reference to a QuestionnaireResponse resource (using sourceReference), if this has been collected in a structured format, using the Questionnaire-Genomic Testing RoD template.
"sourceReference": { "reference": "QuestionnaireResponse/QuestionnaireResponse-RoD-Example" },
policy
For WGS RoD this SHALL be fixed to the below uris.The policyRule element is not expected to be populated for Order Management.
"policy": [ { "authority": "https://www.england.nhs.uk", "uri": "https://www.england.nhs.uk/publication/nhs-genomic-medicine-service-record-of-discussion-form" } ]
provision
Used to reference the ServiceRequest the Consent applies to. SHALL be present where the consent only applies to a specific test."provision": { "data": [ { "meaning": "instance", "reference": { "reference": "ServiceRequest/ServiceRequest-WGSTestOrderForm-Example" } } ] }