Resource Profile: Consent - PowerOfAttorney
General information
Scope and Usage
This profile can be used to carry information about a patient authorizing a related person to act on its behalf.
Boundaries and Relationships
This profile can be referenced to from Permission - ProxyPermission as legal justification for a person being permitted to perform one or more actions on behalf of a patient.
A PowerOfAttorney is always based on an DocumentReference - AuthorizationTemplate, which is referenced to in the sourceReference element.
Profile
| PowerOfAttorneyPoa (Consent) | C | Consent | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | S C | 0..1 | Narrative |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| status | S | 1..1 | codeBindingFixed Value |
| div | S C | 1..1 | xhtml |
| contained | C | 0..* | Resource |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| identifier | S Σ C | 0..1 | Identifier |
| status | S Σ ?! | 1..1 | codeBinding |
| category | S Σ | 0..* | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| subject | S Σ C | 1..1 | Reference(PatientDataAccess) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | S Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | S Σ C | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | S Σ | 1..1 | uri |
| value | S Σ C | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| date | S Σ | 0..1 | date |
| period | S Σ C | 1..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | S Σ C | 1..1 | dateTime |
| end | S Σ C | 0..1 | dateTime |
| grantor | S Σ C | 1..1 | Reference(PatientDataAccess | RelatedPersonDataAccess) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | S Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | S Σ C | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | S Σ | 1..1 | uri |
| value | S Σ C | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| grantee | S Σ C | 1..1 | Reference(RelatedPersonDataAccess) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | S Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | S Σ C | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | S Σ | 1..1 | uri |
| value | S Σ C | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| manager | C | 0..* | Reference(HealthcareService | Organization | Patient | Practitioner) |
| controller | C | 0..* | Reference(HealthcareService | Organization | Patient | Practitioner) |
| sourceAttachment | C | 0..* | Attachment |
| sourceReference | S C | 1..1 | Reference(DocumentReference) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | S Σ C | 1..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | Σ C | 0..1 | Identifier |
| display | Σ C | 0..1 | string |
| regulatoryBasis | 0..* | CodeableConcept | |
| policyBasis | 0..1 | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| reference | C | 0..1 | Reference(Resource) |
| url | 0..1 | url | |
| policyText | C | 0..* | Reference(DocumentReference) |
| verification | SO Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| verified | S Σ | 1..1 | boolean |
| verificationType | S | 0..1 | CodeableConcept |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| verifiedBy | C | 0..1 | Reference(Organization | Practitioner | PractitionerRole) |
| verifiedWith | S C | 1..1 | Reference(Patient | RelatedPerson) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | S Σ C | 1..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | S Σ | 1..1 | uri |
| value | S Σ C | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| verificationDate | 0..* | dateTime | |
| decision | S Σ ?! | 1..1 | codeBindingFixed Value |
| provision | S Σ | 1..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| period | Σ C | 0..1 | Period |
| actor | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| role | 0..1 | CodeableConceptBinding | |
| reference | C | 0..1 | Reference(CareTeam | Device | Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| action | S Σ | 1..* | CodeableConceptBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| coding | S Σ C | 1..1 | Coding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| text | Σ | 0..1 | string |
| securityLabel | Σ C | 0..* | Coding |
| purpose | Σ C | 0..* | CodingBinding |
| documentType | S Σ C | 0..* | CodingBinding |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | S Σ | 1..1 | uri |
| version | Σ | 0..1 | string |
| code | S Σ C | 1..1 | code |
| display | Σ C | 0..1 | string |
| userSelected | Σ | 0..1 | boolean |
| resourceType | Σ C | 0..* | CodingBinding |
| code | Σ | 0..* | CodeableConcept |
| dataPeriod | S Σ C | 0..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | S Σ C | 0..1 | dateTime |
| end | S Σ C | 0..1 | dateTime |
| data | S Σ | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | S Σ | 1..1 | codeBinding |
| reference | S Σ C | 1..1 | Reference(Resource) |
| fromCaregiverOrUnit | S Σ | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| meaning | S Σ | 1..1 | codeBindingFixed Value |
| reference | S Σ C | 1..1 | Reference(OrganizationDataAccess) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | S Σ C | 0..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | S Σ C | 0..1 | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | S Σ | 1..1 | uri |
| value | S Σ C | 1..1 | string |
| period | Σ C | 0..1 | Period |
| assigner | Σ C | 0..1 | Reference(Organization) |
| display | Σ C | 0..1 | string |
| expression | C | 0..1 | Expression |
| provision | 0..* | see (provision) |
| Consent | C | |||||
| Short | A healthcare consumer's or third party'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 or choices made on their behalf by a third party, 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 consent for research participation and data sharing. | |||||
| 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 | Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case. | |||||
| 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 | |||||
| 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 its narrative along with other profiles, value sets, etc. | |||||
| 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 | IETF language tag for 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). | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.text | S C | |||||
| Short | Description of POA | |||||
| 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 | |||||
| Must Support | True | |||||
| Alias | narrative, html, xhtml, display | |||||
| Comments | Contained resources do not have a 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: dom-6 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.text.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.text.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.text.status | S | |||||
| Short | generated | extensions | additional | empty | |||||
| Definition | The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data. | |||||
| Cardinality | 1..1 | |||||
| Type | code | |||||
| Binding | The status of a resource narrative. | |||||
| Must Support | True | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Constraints |
| |||||
| Fixed Value | generated | |||||
| Mappings |
| |||||
| Consent.text.div | S C | |||||
| Short | Limited xhtml content | |||||
| Definition | The actual narrative content, a stripped down version of XHTML. | |||||
| Cardinality | 1..1 | |||||
| Type | xhtml | |||||
| Must Support | True | |||||
| Comments | The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, <a> elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.contained | C | |||||
| 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, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning. | |||||
| 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. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: dom-2, dom-4, dom-3, dom-5 | |||||
| Mappings |
| |||||
| Consent.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.modifierExtension | Σ ?! C | |||||
| 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 managable, 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 | |||||
| Summary | 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.identifier | S Σ C | |||||
| Short | Identifier for this record (external references) | |||||
| Definition | Unique identifier for this copy of the Consent Statement. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.status | S Σ ?! | |||||
| Short | draft | active | inactive | |||||
| Definition | Indicates the current state of this Consent resource. | |||||
| Cardinality | 1..1 | |||||
| Type | code | |||||
| Binding | Indicates the state of the consent. | |||||
| Must Support | True | |||||
| Modifier | True | |||||
| Summary | True | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category | S Σ | |||||
| 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 | 0..* | |||||
| Type | CodeableConcept | |||||
| Binding | A classification of the type of consents found in a consent statement. | |||||
| Must Support | 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.category.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding | S Σ C | |||||
| Short | Code defined by a terminology system | |||||
| Definition | A reference to a code defined by a terminology system. | |||||
| Cardinality | 1..1 | |||||
| Type | Coding | |||||
| Must Support | True | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.category.coding.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.system | S Σ | |||||
| 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 | |||||
| Must Support | True | |||||
| 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.code | S Σ C | |||||
| 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 | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | Need to refer to a particular code in the system. | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.display | Σ C | |||||
| 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 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.category.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject | S Σ C | |||||
| Short | Who the consent applies to | |||||
| Definition | The patient/healthcare practitioner or group of persons to whom this consent applies. | |||||
| Cardinality | 1..1 | |||||
| Type | Reference(PatientDataAccess) | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.subject.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.reference | S Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier | S Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.subject.identifier.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier.use | Σ ?! | |||||
| Short | usual | official | temp | secondary | old (If known) | |||||
| Definition | The purpose of this identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | code | |||||
| Binding | Identifies the purpose for this identifier, if known . | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |||||
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier.type | Σ | |||||
| Short | Description of identifier | |||||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Summary | True | |||||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |||||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier.system | S Σ | |||||
| Short | The namespace for the identifier value | |||||
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |||||
| Cardinality | 1..1 | |||||
| Type | uri | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | |||||
| Comments | Identifier.system is always case sensitive. | |||||
| Constraints |
| |||||
| Examples | Generalhttp://www.acme.com/identifiers/patient | |||||
| Mappings |
| |||||
| Consent.subject.identifier.value | S Σ C | |||||
| Short | The value that is unique | |||||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |||||
| Constraints |
| |||||
| Examples | General123456 | |||||
| Mappings |
| |||||
| Consent.subject.identifier.period | Σ C | |||||
| Short | Time period when id is/was valid for use | |||||
| Definition | Time period during which identifier is/was valid for use. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.identifier.assigner | Σ C | |||||
| Short | Organization that issued id (may be just text) | |||||
| Definition | Organization that issued/manages the identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization) | |||||
| Summary | True | |||||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.subject.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.date | S Σ | |||||
| Short | Fully executed date of the consent | |||||
| Definition | Date the consent instance was agreed to. | |||||
| Cardinality | 0..1 | |||||
| Type | date | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.period | S Σ C | |||||
| Short | Effective period for this Consent | |||||
| Definition | Effective period for this Consent Resource and all provisions unless specified in that provision. | |||||
| Cardinality | 1..1 | |||||
| Type | Period | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Alias | period | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.period.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.period.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.period.start | S Σ C | |||||
| Short | Starting time with inclusive boundary | |||||
| Definition | The start of the period. The boundary is inclusive. | |||||
| Cardinality | 1..1 | |||||
| Type | dateTime | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the low element is missing, the meaning is that the low boundary is not known. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.period.end | S Σ C | |||||
| Short | End time with inclusive boundary, if not ongoing | |||||
| Definition | The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. | |||||
| Cardinality | 0..1 | |||||
| Type | dateTime | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. | |||||
| Meaning when missing | If the end of the period is missing, it means that the period is ongoing | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor | S Σ C | |||||
| Short | Who is granting rights according to the policy and rules | |||||
| Definition | The entity responsible for granting the rights listed in a Consent Directive. | |||||
| Cardinality | 1..1 | |||||
| Type | Reference(PatientDataAccess | RelatedPersonDataAccess) | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Alias | grantor | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.grantor.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.reference | S Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier | S Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.grantor.identifier.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier.use | Σ ?! | |||||
| Short | usual | official | temp | secondary | old (If known) | |||||
| Definition | The purpose of this identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | code | |||||
| Binding | Identifies the purpose for this identifier, if known . | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |||||
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier.type | Σ | |||||
| Short | Description of identifier | |||||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Summary | True | |||||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |||||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier.system | S Σ | |||||
| Short | The namespace for the identifier value | |||||
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |||||
| Cardinality | 1..1 | |||||
| Type | uri | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | |||||
| Comments | Identifier.system is always case sensitive. | |||||
| Constraints |
| |||||
| Examples | Generalhttp://www.acme.com/identifiers/patient | |||||
| Mappings |
| |||||
| Consent.grantor.identifier.value | S Σ C | |||||
| Short | The value that is unique | |||||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |||||
| Constraints |
| |||||
| Examples | General123456 | |||||
| Mappings |
| |||||
| Consent.grantor.identifier.period | Σ C | |||||
| Short | Time period when id is/was valid for use | |||||
| Definition | Time period during which identifier is/was valid for use. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.identifier.assigner | Σ C | |||||
| Short | Organization that issued id (may be just text) | |||||
| Definition | Organization that issued/manages the identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization) | |||||
| Summary | True | |||||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantor.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee | S Σ C | |||||
| Short | Who is agreeing to the policy and rules | |||||
| Definition | The entity responsible for complying with the Consent Directive, including any obligations or limitations on authorizations and enforcement of prohibitions. | |||||
| Cardinality | 1..1 | |||||
| Type | Reference(RelatedPersonDataAccess) | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Alias | grantee | |||||
| Comments | In a fully computable consent, both grantee and grantor will be listed as actors within the consent. The Grantee and Grantor elements are for ease of search only. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.grantee.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.reference | S Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier | S Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.grantee.identifier.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier.use | Σ ?! | |||||
| Short | usual | official | temp | secondary | old (If known) | |||||
| Definition | The purpose of this identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | code | |||||
| Binding | Identifies the purpose for this identifier, if known . | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |||||
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier.type | Σ | |||||
| Short | Description of identifier | |||||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Summary | True | |||||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |||||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier.system | S Σ | |||||
| Short | The namespace for the identifier value | |||||
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |||||
| Cardinality | 1..1 | |||||
| Type | uri | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | |||||
| Comments | Identifier.system is always case sensitive. | |||||
| Constraints |
| |||||
| Examples | Generalhttp://www.acme.com/identifiers/patient | |||||
| Mappings |
| |||||
| Consent.grantee.identifier.value | S Σ C | |||||
| Short | The value that is unique | |||||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |||||
| Constraints |
| |||||
| Examples | General123456 | |||||
| Mappings |
| |||||
| Consent.grantee.identifier.period | Σ C | |||||
| Short | Time period when id is/was valid for use | |||||
| Definition | Time period during which identifier is/was valid for use. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.identifier.assigner | Σ C | |||||
| Short | Organization that issued id (may be just text) | |||||
| Definition | Organization that issued/manages the identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization) | |||||
| Summary | True | |||||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.grantee.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.manager | C | |||||
| Short | Consent workflow management | |||||
| Definition | The actor that manages the consent through its lifecycle. | |||||
| Cardinality | 0..* | |||||
| Type | Reference(HealthcareService | Organization | Patient | Practitioner) | |||||
| Alias | manager | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.controller | C | |||||
| Short | Consent Enforcer | |||||
| Definition | The actor that controls/enforces the access according to the consent. | |||||
| Cardinality | 0..* | |||||
| Type | Reference(HealthcareService | Organization | Patient | Practitioner) | |||||
| Alias | controller | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceAttachment | C | |||||
| Short | Source from which this consent is taken | |||||
| Definition | The source on which this consent statement is based. The source might be a scanned original paper form. | |||||
| Cardinality | 0..* | |||||
| Type | Attachment | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference | S C | |||||
| Short | Source from which this consent is taken | |||||
| Definition | A reference to a consent that links back to such a source, a reference to a document repository (e.g. XDS) that stores the original consent document. | |||||
| Cardinality | 1..1 | |||||
| Type | Reference(DocumentReference) | |||||
| Must Support | 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.sourceReference.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference.reference | S Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference.identifier | Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.sourceReference.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.regulatoryBasis | ||||||
| Short | Regulations establishing base Consent | |||||
| Definition | A set of codes that indicate the regulatory basis (if any) that this consent supports. | |||||
| Cardinality | 0..* | |||||
| Type | CodeableConcept | |||||
| Binding | Regulatory policy examples | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyBasis | ||||||
| Short | Computable version of the backing policy | |||||
| Definition | A Reference or URL used to uniquely identify the policy the organization will enforce for this Consent. This Reference or URL should be specific to the version of the policy and should be dereferencable to a computable policy of some form. | |||||
| Cardinality | 0..1 | |||||
| Type | BackboneElement | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyBasis.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.policyBasis.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyBasis.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyBasis.reference | C | |||||
| Short | Reference backing policy resource | |||||
| Definition | A Reference that identifies the policy the organization will enforce for this Consent. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Resource) | |||||
| Comments | While any resource may be used, Consent, PlanDefinition and Contract would be most frequent | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyBasis.url | ||||||
| Short | URL to a computable backing policy | |||||
| Definition | A URL that links to a computable version of the policy the organization will enforce for this Consent. | |||||
| Cardinality | 0..1 | |||||
| Type | url | |||||
| Comments | see http://en.wikipedia.org/wiki/Uniform_resource_identifier | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.policyText | C | |||||
| Short | Human Readable Policy | |||||
| Definition | A Reference to the human readable policy explaining the basis for the Consent. | |||||
| Cardinality | 0..* | |||||
| Type | Reference(DocumentReference) | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification | SO Σ | |||||
| 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..* | |||||
| Type | BackboneElement | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Obligations |
| |||||
| 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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.verification.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verified | S Σ | |||||
| Short | Has been verified | |||||
| Definition | Has the instruction been verified. | |||||
| Cardinality | 1..1 | |||||
| Type | boolean | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType | S | |||||
| Short | Business case of verification | |||||
| Definition | Extensible list of verification type starting with verification and re-validation. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | Types of Verification/Validation. | |||||
| Must Support | True | |||||
| Comments | This allows the verification element to hold multiple use cases including RelatedPerson verification of the Grantee decision and periodic re-validation of the consent. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.verification.verificationType.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding | S Σ C | |||||
| Short | Code defined by a terminology system | |||||
| Definition | A reference to a code defined by a terminology system. | |||||
| Cardinality | 1..1 | |||||
| Type | Coding | |||||
| Must Support | True | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.system | S Σ | |||||
| 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 | |||||
| Must Support | True | |||||
| 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.code | S Σ C | |||||
| 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 | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | Need to refer to a particular code in the system. | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.display | Σ C | |||||
| 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 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationType.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedBy | C | |||||
| Short | Person conducting verification | |||||
| Definition | The person who conducted the verification/validation of the Grantor decision. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization | Practitioner | PractitionerRole) | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith | S C | |||||
| Short | Person who verified | |||||
| Definition | Who verified the instruction (Patient, Relative or other Authorized Person). | |||||
| Cardinality | 1..1 | |||||
| Type | Reference(Patient | RelatedPerson) | |||||
| Must Support | True | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.reference | Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier | S Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 1..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.use | Σ ?! | |||||
| Short | usual | official | temp | secondary | old (If known) | |||||
| Definition | The purpose of this identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | code | |||||
| Binding | Identifies the purpose for this identifier, if known . | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |||||
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.type | Σ | |||||
| Short | Description of identifier | |||||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Summary | True | |||||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |||||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.system | S Σ | |||||
| Short | The namespace for the identifier value | |||||
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |||||
| Cardinality | 1..1 | |||||
| Type | uri | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | |||||
| Comments | Identifier.system is always case sensitive. | |||||
| Constraints |
| |||||
| Examples | Generalhttp://www.acme.com/identifiers/patient | |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.value | S Σ C | |||||
| Short | The value that is unique | |||||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |||||
| Constraints |
| |||||
| Examples | General123456 | |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.period | Σ C | |||||
| Short | Time period when id is/was valid for use | |||||
| Definition | Time period during which identifier is/was valid for use. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.identifier.assigner | Σ C | |||||
| Short | Organization that issued id (may be just text) | |||||
| Definition | Organization that issued/manages the identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization) | |||||
| Summary | True | |||||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verifiedWith.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.verification.verificationDate | ||||||
| Short | When consent verified | |||||
| Definition | Date(s) verification was collected. | |||||
| Cardinality | 0..* | |||||
| Type | dateTime | |||||
| Comments | Allows for history of verification/validation. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.decision | S Σ ?! | |||||
| Short | deny | permit | |||||
| Definition | Action to take - permit or deny - as default. | |||||
| Cardinality | 1..1 | |||||
| Type | code | |||||
| Binding | Sets the base decision for Consent to be either permit or deny, with provisions assumed to be a negation of the previous level. | |||||
| Must Support | True | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Constraints |
| |||||
| Fixed Value | permit | |||||
| Mappings |
| |||||
| Consent.provision | S Σ | |||||
| Short | Constraints to the base Consent.policyRule/Consent.policy | |||||
| Definition | An exception to the base policy of this consent. An exception can be an addition or removal of access permissions. | |||||
| Cardinality | 1..* | |||||
| Type | BackboneElement | |||||
| Must Support | True | |||||
| Summary | True | |||||
| 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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.period | Σ C | |||||
| Short | Timeframe for this provision | |||||
| Definition | Timeframe for this provision. | |||||
| Cardinality | 0..1 | |||||
| Type | Period | |||||
| Summary | True | |||||
| Comments | This is the bound effective time of the consent and should be in the base provision in the Consent resource. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.actor | ||||||
| Short | Who|what controlled by this provision (or group, by role) | |||||
| Definition | Who or what is controlled by this provision. 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 | |||||
| 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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.actor.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.actor.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| 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 | 0..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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.actor.reference | C | |||||
| 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 | 0..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 resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action | S Σ | |||||
| Short | Actions controlled by this provision | |||||
| Definition | Actions controlled by this provision. | |||||
| Cardinality | 1..* | |||||
| Type | CodeableConcept | |||||
| Binding | Detailed codes for the consent action. | |||||
| Must Support | True | |||||
| 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.action.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding | S Σ C | |||||
| Short | Code defined by a terminology system | |||||
| Definition | A reference to a code defined by a terminology system. | |||||
| Cardinality | 1..1 | |||||
| Type | Coding | |||||
| Must Support | True | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.action.coding.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.system | S Σ | |||||
| 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 | |||||
| Must Support | True | |||||
| 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.code | S Σ C | |||||
| 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 | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | Need to refer to a particular code in the system. | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.display | Σ C | |||||
| 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 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.coding.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.action.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.securityLabel | Σ C | |||||
| 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 | Example 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.purpose | Σ C | |||||
| Short | Context of activities covered by this provision | |||||
| Definition | The context of the activities a user is taking - why the user is accessing the data - that are controlled by this provision. | |||||
| 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. http://terminology.hl7.org/ValueSet/v3-PurposeOfUse (extensible) | |||||
| Summary | True | |||||
| Comments | When the purpose of use tag is on the data, access request purpose of use shall not conflict. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType | S Σ C | |||||
| Short | EHDS data category | |||||
| Definition | The documentType(s) covered by this provision. The type can be a CDA document, or some other type that indicates what sort of information the consent relates to. | |||||
| Cardinality | 0..* | |||||
| Type | Coding | |||||
| Binding | The document type a consent provision covers. | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Multiple types are or'ed together. The intention of the documentType element is that the codes refer to document types defined in a standard somewhere. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.documentType.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.system | S Σ | |||||
| 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 | |||||
| Must Support | True | |||||
| 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 be an absolute reference to some definition that establishes the system clearly and unambiguously. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.code | S Σ C | |||||
| 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 | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | Need to refer to a particular code in the system. | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.display | Σ C | |||||
| 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 1,048,576 (1024*1024) characters in size | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cod-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.documentType.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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.resourceType | Σ C | |||||
| Short | e.g. Resource Type, Profile, etc | |||||
| Definition | The resourceType(s) covered by this provision. The type can be a FHIR resource type or a profile on a type that indicates what information the consent relates to. | |||||
| Cardinality | 0..* | |||||
| Type | Coding | |||||
| Binding | The resource types a consent provision covers. | |||||
| Summary | True | |||||
| Comments | Multiple types are or'ed together. The intention of the resourceType element is that the codes refer to profiles or document types defined in a standard or an implementation guide somewhere. | |||||
| 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 provision applies. | |||||
| Cardinality | 0..* | |||||
| Type | CodeableConcept | |||||
| Binding | If this code is found in an instance, then the exception applies. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.dataPeriod | S Σ C | |||||
| Short | Timeframe for data controlled by this provision | |||||
| Definition | Clinical or Operational Relevant period of time that bounds the data controlled by this provision. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.dataPeriod.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.dataPeriod.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.dataPeriod.start | S Σ C | |||||
| Short | Starting time with inclusive boundary | |||||
| Definition | The start of the period. The boundary is inclusive. | |||||
| Cardinality | 0..1 | |||||
| Type | dateTime | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the low element is missing, the meaning is that the low boundary is not known. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.dataPeriod.end | S Σ C | |||||
| Short | End time with inclusive boundary, if not ongoing | |||||
| Definition | The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. | |||||
| Cardinality | 0..1 | |||||
| Type | dateTime | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. | |||||
| Meaning when missing | If the end of the period is missing, it means that the period is ongoing | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: per-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data | S Σ | |||||
| Short | Data controlled by this provision | |||||
| Definition | The resources controlled by this provision if specific resources are referenced. | |||||
| Cardinality | 0..* | |||||
| Type | BackboneElement | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Meaning when missing | all data | |||||
| Slicing | Unordered, Open, by meaning(Value) Slice data based on meaning | |||||
| 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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.data.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data.meaning | S Σ | |||||
| 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. | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data.reference | S Σ C | |||||
| 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) | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit | S Σ | |||||
| Short | Data controlled by this provision | |||||
| Definition | The resources controlled by this provision if specific resources are referenced. | |||||
| Cardinality | 0..* | |||||
| Type | BackboneElement | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Meaning when missing | all data | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.modifierExtension | Σ ?! C | |||||
| 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 managable, 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.meaning | S Σ | |||||
| 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. | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Note that FHIR strings SHALL NOT exceed 1,048,576 (1024*1024) characters in size | |||||
| Constraints |
| |||||
| Fixed Value | authoredby | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference | S Σ C | |||||
| 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(OrganizationDataAccess) | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolvable (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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.reference | S Σ C | |||||
| Short | Literal reference, Relative, internal or absolute URL | |||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2, ref-1 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.type | Σ | |||||
| Short | Type the reference refers to (e.g. "Patient") - must be a resource in resources | |||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | |||||
| Cardinality | 0..1 | |||||
| Type | uri | |||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | |||||
| Summary | True | |||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a known RESTful URL) or by resolving the target of the reference. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier | S Σ C | |||||
| Short | Logical reference, when literal reference is not known | |||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | |||||
| Cardinality | 0..1 | |||||
| Type | Identifier | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). This element only allows for a single identifier. In the case where additional identifers are required, use the http://hl7.org/fhir/StructureDefinition/additionalIdentifier extension. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.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 | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.extension | C | |||||
| 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 managable, 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 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.use | Σ ?! | |||||
| Short | usual | official | temp | secondary | old (If known) | |||||
| Definition | The purpose of this identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | code | |||||
| Binding | Identifies the purpose for this identifier, if known . | |||||
| Modifier | True | |||||
| Summary | True | |||||
| Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. | |||||
| Comments | Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.type | Σ | |||||
| Short | Description of identifier | |||||
| Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Cardinality | 0..1 | |||||
| Type | CodeableConcept | |||||
| Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. | |||||
| Summary | True | |||||
| Requirements | Allows users to make use of identifiers when the identifier system is not known. | |||||
| Comments | This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.system | S Σ | |||||
| Short | The namespace for the identifier value | |||||
| Definition | Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique. | |||||
| Cardinality | 1..1 | |||||
| Type | uri | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Requirements | There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. | |||||
| Comments | Identifier.system is always case sensitive. | |||||
| Constraints |
| |||||
| Examples | Generalhttp://www.acme.com/identifiers/patient | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.value | S Σ C | |||||
| Short | The value that is unique | |||||
| Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. | |||||
| Cardinality | 1..1 | |||||
| Type | string | |||||
| Must Support | True | |||||
| Summary | True | |||||
| Comments | If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ident-1 | |||||
| Constraints |
| |||||
| Examples | General123456 | |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.period | Σ C | |||||
| Short | Time period when id is/was valid for use | |||||
| Definition | Time period during which identifier is/was valid for use. | |||||
| 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. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.identifier.assigner | Σ C | |||||
| Short | Organization that issued id (may be just text) | |||||
| Definition | Organization that issued/manages the identifier. | |||||
| Cardinality | 0..1 | |||||
| Type | Reference(Organization) | |||||
| Summary | True | |||||
| Comments | The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.data:fromCaregiverOrUnit.reference.display | Σ C | |||||
| Short | Text alternative for the resource | |||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | |||||
| Cardinality | 0..1 | |||||
| Type | string | |||||
| Summary | True | |||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | |||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ref-2 | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.expression | C | |||||
| Short | A computable expression of the consent | |||||
| Definition | A computable (FHIRPath or other) definition of what is controlled by this consent. | |||||
| Cardinality | 0..1 | |||||
| Type | Expression | |||||
| Comments | Constraining the expression type for a specific implementation via profile is recommended | |||||
| Constraints |
| |||||
| Mappings |
| |||||
| Consent.provision.provision | ||||||
| Short | Nested Exception Provisions | |||||
| Definition | Provisions which provide exceptions to the base provision or subprovisions. | |||||
| Cardinality | 0..* | |||||
| Type | see (provision) | |||||
Details
The red must-support flag ("S") indicates that the element is expected in some use cases, and a missing flag that the element is never used.
The following sections describe how to use the profile to build a PowerOfAttorney.
Verification
The grantor, grantee and potential other parties (e.g. a second guardian if the grantor is the first guardian) have to verify that the content in the PowerOfAttorney is valid before it becomes active. The POA Source Actor is responsible for populating the verification element with the parties expected to verify by adding their identifiers to the verification.verifiedWith element.
A party supplied in the verification element has to either sign or consent. See operation GetSignatureRequest on how to initiate the signing process and RegisterSignatureResponse on how to finish the signing process. See operation RegisterGranteeConsent on how to register the grantee consenting to the PowerOfAttorney. The verification.verified flag will be true when the party has signed or consented.
Status
On whose behalf are actions being authorized
To define on whose behalf the actions are being authorized, use the subject element. To reference the patient using an existing external identifier, the system of the identifier and the value should be provided. The system ID declares what type of identifier the patient identifier is.
{
[...]
"subject": {
"identifier": {
"system": "http://electronichealth.se/identifier/personnummer",
"value": "198001032385"
}
}
}
Current valid patient identifiers are:
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, e.g. 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, e.g. 201903682399
Who created the power of attorney
To define who created the PowerOfAttorney, use the grantor element. Valid grantors are the patient itself and an authorized person related to the patient.
{
[...]
"grantor": {
"identifier": {
"system": "http://electronichealth.se/identifier/personnummer",
"value": "198001032385"
}
}
}
Current valid identifiers are:
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, e.g. 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, e.g. 201903682399
Who is being authorized
To define who is being authorized to act on the patients behalf, the element grantee should be used. A grantee is always a person related to the patient.
To reference the grantee's existing external identifier, the system of the identifier and the value should be provided. The system ID declares what type of identifier the external identifier is.
{
[...]
"grantee": {
"identifier": {
"system": "http://electronichealth.se/identifier/personnummer",
"value": "198001032385"
}
}
}
Current valid identifiers are:
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, e.g. 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, e.g. 201903682399
During what time frame is power of attorney valid
To define when the PowerOfAttorney is valid, use the period element. Note that a start time for the PowerOfAttorney has to be supplied. If an end time is not supplied, the PowerOfAttorney should be interpreted as indefinite.
{
[...]
"period": {
"start": "2026-11-12",
"end": "2027-11-12"
}
}
What actions are being authorized
To define what actions are being authorized to be performed on behalf of the patient, use the provision.action element. Use codes from value set Aktiviteter som företrädarskap innefattar.
To what data are actions being authorized
The following sections describe how to define the data on which the actions can be performed. This can be done by specifying what source the data has, what category of data it is and when the data was registered. These filters can be combined.
Define data by its source
To define a PowerOfAttorney that authorizes actions on data from a certain source the provision.data element should be used. A data source can be a care giver, care unit or country. The data element contains a reference that can reference to the source as a Organization. The data element also contains a meaning element that should be set to authoredby to specify that the reference is a data source.
If a data source is not supplied, the data definition should be interpreted to regard data from any data source and that matches the other data filters.
{
[...]
"provision": [
{
"data": [
{
"reference": {
"identifier": {
"system": "urn:oid:2.5.4.97",
"value": "2021005389"
}
},
"meaning": "authoredby"
}
]
}
]
}
Country
If the source is a country, current valid identifiers are:
- Country code according to ISO-3166
- system: urn:iso:std:iso:3166
- value format: 2 characters, e.g. SE
Healthcare provider
If the source is a healthcare provider, current valid identifiers are:
- Organization identifier (sv: organisationsnummer)
- system: urn:oid:2.5.4.97
- value format: 10 digits without hyphen, e.g. 2021005389
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, e.g. 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, e.g. 201903682399
Healthcare unit
If the source is a healthcare unit, current valid identifiers are:
- HSA ID
- system: urn:oid:1.2.752.29.4.19
- value format: SE+10 digits+hyphen+a number of alphanumerical characters, e.g. SE1234567890-ABC1
Define data by information category
To define a PowerOfAttorney that authorizes actions on data of a certain information category the provision.documentType element should be used. Use codes from value set Datakategorier enligt EHDS.
If an information category is not supplied, the data definition should be interpreted to regard data of all information categories and that matches the other data filters.
{
[...]
"provision": [
{
"documentType": [
{
"system": "<code system>",
"code": "<information category code>"
}
]
}
]
}
Define data by date of registration
To define a PowerOfAttorney that authorizes actions on data that was registered within a certain time interval, use the provision.dataPeriod element. An empty start element when end has been set should be interpreted as data registered at any time before the set end. An empty end element when start has been set should be interpreted as data registered at any time after the set start.
If a time interval is not supplied, the data definition should be interpreted to regard data from any point in time and that matches the other data filters.
{
[...]
"provision": [
{
"dataPeriod": [
{
"start": "2025-08-01",
"end": "2025-11-01"
}
]
}
]
}
Reference to instance of data
To define a PowerOfAttorney that authorizes actions on a specific piece of data the provision.data element should be used. The data element contains a reference that can reference to an instance of for example an observation or a diagnosis. The meaning should be set to instance to specify that the reference is a data instance.
If a reference to an instance is not supplied, the data definition should be interpreted to regard all data that matches the other data filters.
{
[...]
"provision": [
{
"data": [
{
"reference": {
"reference": "Observation/02d9860a-18a8-43a2-a961-04219650e72c"
},
"meaning": "instance"
}
]
}
]
}
ValueSet bindings
The following table shows the elements in the profile that should be populated with codes as well as what value sets contain the valid codes for the respective elements. The strength indicates whether it is recommended or required to choose a code from the defined value set.
| Path | Strength | ValueSet |
|---|---|---|
| Consent.status | required | http://electronichealth.se/fhir/NDI/ValueSet/poa-poa-statuses |
| Consent.provision.action | required | http://electronichealth.se/fhir/NDI/ValueSet/ps-permission-actions |
| Consent.provision.documentType | required | http://electronichealth.se/fhir/NDI/ValueSet/ndi-ehds-categories |
Validation rules
This section contains validation rules for the format of a PowerOfAttorneyDocument along with corresponding error messages. The error messages are returned in a OperationOutcome. An OperationOutcome contains an array of issues where each issue has a details element containing an error message and when relevant an expression element containing the path to the element which the error pertains to.
General
This section contains error messages when violating general conformance rules defined in the profile, such as cardinality.
| Description | Error message | Severity |
|---|---|---|
| Cardinality of elements must be followed | 2-XX-1: Attribut har kardinalitet %s men har angivits %s gånger. | Error |
| Code must be from required value set | 2-XX-8: Ogiltig kod | Error |
| Identifier systems must be be from list of valid systems (see Details section above) | 2-XX-4: Ogiltigt system-ID | Error |
Invariants
Invariants express additional constraints in the profile which cannot be expressed using cardinality, data types and terminology bindings. These rules can pertain to for example valid value formats based on certain conditions and valid combinations of elements.
| Rule ID | Element | Description | Error message | Severity | Expression |
|---|---|---|---|---|---|
| ndi-personal-identity-number-value-1 | Consent.grantee.identifier, Consent.grantor.identifier, Consent.subject.identifier, Consent.provision.data.reference.identifier | A Swedish personal identity number (sv: personnummer) should follow format 198001032385 | 2-XX-2: Ogiltigt format på personnummer. Ange tolvsiffriga personnumret utan bindestreck, t. ex. 198001032385. | Error | value.matches('^([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(0[1-9]|1[0-2])(0[1-9]|[1-2][0-9]|3[0-1])\\d{4}$') or system != 'http://electronichealth.se/identifier/personnummer' |
| ndi-consent-period-end-1 | Consent.period.end | Period.end SHALL have a higher or equal value than today's date | 2-XX-15: Start- och slutdatum får inte vara passerade datum. | Error | $this >= today() |
| ndi-consent-period-start-1 | Consent.period.start | Period.start SHALL have a higher or equal value than today's date | 2-XX-15: Start- och slutdatum får inte vara passerade datum. | Error | $this >= today() |
| ndi-coordination-number-value-1 | Consent.grantee.identifier, Consent.grantor.identifier, Consent.subject.identifier | A Swedish coordination number (sv: samordningsnummer) should follow format 201903682399 | 2-XX-3: Ogiltigt format på samordningsnummer. Ange tolvsiffriga samordningsnumret utan bindestreck, t. ex. 198000602394. | Error | value.matches('^([0-9]([0-9]([0-9][1-9]|[1-9]0)|[1-9]00)|[1-9]000)(0[1-9]|1[0-2])([6-9][1-9])\\d{4}$') or system != 'http://electronichealth.se/identifier/samordningsnummer' |
| ndi-dateTime-1 | Consent.period.start, Consent.period.end, Consent.provision.dataPeriod.start, Consent.provision.dataPeriod.end | DateTime must be a valid date that follows format YYYY-MM-DD without timestamp | 2-XX-13: Datum ska vara ett giltigt datum som anges på formatet YYYY-MM-DD utan tidsangivelse | Error | $this.matches('^\\d{4}-\\d{2}-\\d{2}$') |
| ndi-organization-identifier-value-1 | Consent.provision.data.reference.identifier | A Swedish organization identifier (sv: organisationsnummer) should follow format 7999000057 | 2-XX-12: Ogiltigt format på organisationsnummer. Ange tiosiffriga organisationsnumret utan bindestreck, t. ex. 9966353346. | Error | value.matches('^\\d{6}\\d{4}$') or system != 'urn:oid:2.5.4.97' |
| per-1 | Consent.period, Consent.dataPeriod | If present, start SHALL have a lower or equal value than end | 2-XX-16: Slutdatum måste vara samtidigt som eller senare än startdatum. | Error | start.hasValue().not() or end.hasValue().not() or (start.lowBoundary() <= end.highBoundary()) |
Business rules
| Element | Description | Error message | Severity |
|---|---|---|---|
| Consent.grantee | Grantee of Consent must be at least 18 years old | 2-XX-9: Fullmaktshavaren måste ha fyllt 18 år. | Error |
Examples
PowerOfAttorney verified by both parties
The following example of PowerOfAttorney shows an instance that has been verified by both grantor and grantee, ie signed by grantor and consented to by grantee, as seen in the two verification elements.
| Consent |
| id : 57d8e572-7dab-469a-ab33-ddeb7ad2a6b2 |
| text |
| status : generated |
| status : active |
| subject |
| identifier |
| system : http://electronichealth.se/identifier/personnummer |
| value : 199001232389 |
| date : 2025-11-21 |
| period |
| start : 2025-12-01 |
| end : 2026-05-01 |
| grantor |
| identifier |
| system : http://electronichealth.se/identifier/personnummer |
| value : 199001232389 |
| grantee |
| identifier |
| system : http://electronichealth.se/identifier/personnummer |
| value : 198001032385 |
| sourceReference |
| reference : DocumentReference/333117b6-1f15-4719-9a72-f118efe93781/_history/e6973375-738d-436b-8e34-7c4e96c0f110 |
| verification |
| verified : True |
| verifiedWith |
| identifier |
| system : http://electronichealth.se/identifier/personnummer |
| value : 198001032385 |
| verification |
| verified : True |
| verifiedWith |
| identifier |
| system : http://electronichealth.se/identifier/personnummer |
| value : 199001232389 |
| decision : permit |
| provision |
| action |
| coding |
| system : http://terminology.hl7.org/CodeSystem/consentaction |
| code : access |
| documentType |
| system : https://electronichealth.se/ndi/CodeSystem/ndi-ehds-priority-category |
| code : laboratory-results |
| dataPeriod |
| start : 2025-08-01 |
| data |
| meaning : authoredby |
| reference |
| identifier |
| system : urn:oid:2.5.4.97 |
| value : 165560269986 |
Supported operations
HTTP methods
The following table explains what HTTP methods can be done on the Consent resource using this profile.
| Operation | Supported | Comment |
|---|---|---|
| Search (GET, POST) | yes | |
| Insert (POST) | yes | |
| Update (PUT) | no | Use operations to update |
| Delete (DEL) | no | Use operation RevokeConsent to set status to inactive |
| Operation (GET, POST) | yes |
Query operations
Supported Queries
GET [base]/Consent/[LogicalId]returns the Consent with the supplied logical ID if found, otherwise a 404 HTTP status code.GET [base]/Consent?patient:identifier=[system]|[value]{&[parameters]}returns a Bundle of Consents where the patient with supplied identifier is the subject of the Consent and that match the additional parameters if any. If no Consents are found the Bundle will be empty.GET [base]/Consent?grantee:identifier=[system]|[value]{&[parameters]}returns a Bundle of Consents where the grantee with supplied identifier is the grantee of the Consent and that match the additional parameters if any. If no Consents are found the Bundle will be empty.
Search parameters
| Parameter | Description | Example |
|---|---|---|
| grantee:identifier | Identifier of grantee of Consent, as "system|value" | grantee:identifier=http://electronichealth.se/identifier/personnummer|198001012345 |
| patient:identifier | Identifier of subject of Consent, as "system|value" | patient:identifier=http://electronichealth.se/identifier/personnummer|198001012345 |
| status | Status of Consent. Must be from Status på fullmakt. multipleOR SHALL be supported. |
status=active |
Validation rules
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome resource, in the issue.details element. The issue.expression element should point to which parameter the issue pertains to.
| Parameter | Error message | Description | Severity |
|---|---|---|---|
| grantee:identifier, patient:identifier | 2-XX-2: Ogiltigt format på personnummer. Ange tolvsiffriga personnumret utan bindestreck, t. ex. 198001032385. | Personal identity number should be 12 digits without hyphen | Error |
| grantee:identifier, patient:identifier | 2-XX-3: Ogiltigt format på samordningsnummer. Ange tolvsiffriga samordningsnumret utan bindestreck, t. ex. 201903682399. | Coordination number should be 12 digits without hyphen | Error |
| grantee:identifier, patient:identifier | 2-XX-4: Ogiltigt system-ID. | The identifier system value must be be from list of valid systems (see section "Details" above) | Error |
Create operations
To create a PowerOfAttorney, use the following invocation:
POST [base]/Consent
The PowerOfAttorney should be supplied in the request body. The server SHALL return a Location header with the logical ID of the created resource in the following format: Location: [base]/Consent/[id]
Other operations
RegisterGranteeConsent
Register grantee of PowerOfAttorney consenting to the content of the power of attorney.
Invocations
POST [base]/Consent/[id]/$register-grantee-consent
Return Values (Out)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| return | 1..1 | OperationOutcome | Outcome of operation |
Validation messages
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome resource.
| Parameter | Error message | Description | Severity |
|---|---|---|---|
| id | 2-XX-5: Parametern %s saknas. | Parameters with cardinality 1..N must be supplied | Error |
| id | 2-XX-6: Fullmakt med id %s hittades inte | PowerOfAttorney with supplied logical ID not found | Error |
| 2-XX-7: Fullmaktsgivare måste ha signerat innehållet innan fullmaktshavare kan samtycka | Patient must have signed the PowerOfAttorney before the grantee can consent | Error | |
| 2-XX-14: En återkallad fullmakt kan inte ändras. | A PowerOfAttorney that has been revoked cannot be altered. | Error | |
| 4-XX-1: Samtyckte registrerat | Consent registered successfully | Success |
GetSignatureRequest
Gets SAML signature request of a PowerOfAttorney.
Invocations
POST [base]/Consent/[id]/$get-signature-request
Parameters (In)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| acsEndpointUrl | 1..1 | url | URL where identity provider should send response to after user has signed |
| identityProvider | 1..1 | Coding | Identity provider to use for signing. Must come from value set Identitetsleverantörer för signering |
| signer | 1..1 | Identifier | Identifier of person whose signature the request is for, with system and value. |
Return Values (Out)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| eidSignRequest | 1..1 | base64Binary | Base64 encoded signature request |
| targetUrl | 1..1 | url | URL to signing service |
| relayState | 1..1 | string | Hex of signing request |
| binding | 1..1 | string | Binding specification of signing service |
Validation messages
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome resource.
| Parameter | Error message | Description | Severity |
|---|---|---|---|
| acsEndpointUrl, identityProvider | 2-XX-5: Parametern %s saknas. | Parameters with cardinality 1..N must be supplied | Error |
| id | 2-XX-6: Fullmakt med id %s hittades inte | PowerOfAttorney with supplied logical ID not found | Error |
| identityProvider | 2-XX-8: Ogiltig kod | Code must be from required value set | Error |
| 2-XX-14: En återkallad fullmakt kan inte ändras. | A PowerOfAttorney that has been revoked cannot be signed. | Error | |
| signer | 2-XX-17: Angiven person är inte en av parterna som ska signera fullmakten. | Supplied signer is not supposed to sign the PowerOfAttorney. | Error |
Examples of requests
Invocation: POST [base]/Consent/ed3cbdbb-97de-4573-b9e0-d7422b8c2696/$get-signature-request
Request body:
| Parameters |
| id : GetSignatureRequest-BankId-RequestBody |
| parameter |
| name : identityProvider |
| value |
| system : http://electronichealth.se/CodeSystem/identity-providers |
| code : BANKID |
| parameter |
| name : acsEndpointUrl |
| value : http://client.example.com/api/acs |
| parameter |
| name : signer |
| value |
| system : http://electronichealth.se/identifier/samordningsnummer |
| value : 201903682399 |
Examples of responses
Successful operation
A successful operation returns a Parameters resource containing the return values.
| Parameters |
| id : 3dbc6217-82c1-486a-93ee-1772cb8cd392 |
| parameter |
| name : eidSignRequest |
| value : PFNpZ25SZXF1ZXN0Cg== |
| parameter |
| name : targetUrl |
| value : https://ehalsomyndigheten.dss.signport-qa.se/sign/BeginSigning |
| parameter |
| name : relayState |
| value : c928e6123eb0431ca8e1df5ba9c1ee76 |
| parameter |
| name : binding |
| value : POST/XML/1.0 |
Failed operation
A failed operation returns an OperationOutcome.
The following example shows a response when the supplied logical ID was not found. The issue.code element is set to "not-found" and the issue.details contains the appropriate error message.
| OperationOutcome |
| id : c98d0d69-ea3c-4e7c-b0d5-f521defe1ef0 |
| issue |
| severity : error |
| code : not-found |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 2-XX-6 |
| display : Fullmakt med id ed3cbdbb-97de-4573-b9e0-d7422b8c2696 hittades inte. |
The following example shows a response when an invalid code was supplied in the identityProvider parameter. The issue.code element is set to "value", the issue.expression element declares which element the issue pertains to - i.e. the element valueCode of the second (indexing starts at 0) parameter in the Parameters request body - and the issue.details contains the appropriate error message.
| OperationOutcome |
| id : 0e1f84be-2595-4d30-b302-5bb6ee352ef7 |
| issue |
| severity : error |
| code : value |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 2-XX-4 |
| display : Ogiltigt system-ID. |
| expression : Parameters.parameter[0].resource.entry[0].resource.grantee.identifier.system |
RegisterSignatureResponse
Registers SAML signature response.
Invocations
POST [base]/Consent/$register-signature-response
Parameters (In)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| eidSignResponse | 1..1 | base64Binary | Base64 encoded signature response |
| relayState | 1..1 | string | UUID of signing request |
| binding | 1..1 | string | Binding specification of signing service |
Return Values (Out)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| return | 1..1 | OperationOutcome | OperationOutcome with result of operation |
Validation messages
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome resource.
| Parameter | Error message | Description | Severity |
|---|---|---|---|
| eidSignResponse, relayState, binding | 2-XX-5: Parametern %s saknas. | Parameters with cardinality 1..N must be supplied | Error |
| id | 2-XX-6: Fullmakt med id %s hittades inte | PowerOfAttorney with supplied logical ID not found | Error |
| 2-XX-10: Ogiltig signaturrespons | Operation failed because of invalid combination of signature response, relay state and binding | Error | |
| 2-XX-14: En återkallad fullmakt kan inte ändras. | A PowerOfAttorney that has been revoked cannot be signed. | Error | |
| 4-XX-301: Signering avklarad | Signing completed successfully | Success |
Examples of requests
Invocation: POST [base]/Consent/$register-signature-response
Request body:
| Parameters |
| id : RegisterSignatureResponse-PostXmlBinding-RequestBody |
| parameter |
| name : eidSignRequest |
| value : PFNpZ25SZXF1ZXN0Cg== |
| parameter |
| name : relayState |
| value : c928e6123eb0431ca8e1df5ba9c1ee76 |
| parameter |
| name : binding |
| value : POST/XML/1.0 |
Examples of responses
Successful operation
A successful operation returns an OperationOutcome with issue.severity and issue.code both set to "success".
| OperationOutcome |
| id : 766dc546-decc-4ee3-9484-c238b9e6c6e7 |
| issue |
| severity : success |
| code : success |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 4-XX-301 |
| display : Signering avklarad |
Failed operation
A failed operation returns an OperationOutcome.
The following example shows a response when the supplied logical ID was not found. The issue.code element is set to "not-found" and the issue.details contains the appropriate error message.
| OperationOutcome |
| id : c98d0d69-ea3c-4e7c-b0d5-f521defe1ef0 |
| issue |
| severity : error |
| code : not-found |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 2-XX-6 |
| display : Fullmakt med id ed3cbdbb-97de-4573-b9e0-d7422b8c2696 hittades inte. |
The following example shows a response when the signing failed because of invalid combination of signature response, relay state and binding values.
| OperationOutcome |
| id : 45868e4a-cd4d-4c0f-978f-422e8059973b |
| issue |
| severity : error |
| code : processing |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 2-XX-10 |
| display : Ogiltig signeringsrespons |
RevokeConsent
Revokes a Consent resource.
Revoking a PowerOfAttorney will set its status to inactive. A PowerOfAttorney can only be revoked by the grantor or grantee.
Invocations
POST [base]/Consent/[id]/$revoke
Parameters (In)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| revokedBy | 1..1 | Identifier (system and value) | Identifier of person who is revoking the Consent, with system and value. |
Current valid identifiers are:
- Personal identity number (sv: personnummer)
- system: http://electronichealth.se/identifier/personnummer
- value format: 12 digits without hyphen, e.g. 198001032385
- Coordination number (sv: samordningsnummer)
- system: http://electronichealth.se/identifier/samordningsnummer
- value format: 12 digits without hyphen, e.g. 201903682399
Return Values (Out)
| Name | Cardinality | Type | Documentation |
|---|---|---|---|
| return | 1..1 | OperationOutcome | OperationOutcome with result of operation |
Validation messages
Validation messages are error, information or success messages that are returned as a result of an operation. These messages are returned in a OperationOutcome resource.
| Parameter | Error message | Description | Severity |
|---|---|---|---|
| revokedBy.valueIdentifier.value | 2-XX-2: Ogiltigt format på personnummer. Ange tolvsiffriga personnumret utan bindestreck, t. ex. 198001032385. | Personal identity number should be 12 digits without hyphen | Error |
| revokedBy.valueIdentifier.value | 2-XX-3: Ogiltigt format på samordningsnummer. Ange tolvsiffriga samordningsnumret utan bindestreck, t. ex. 201903682399. | Coordination number should be 12 digits without hyphen | Error |
| revokedBy.valueIdentifier.system | 2-XX-4: Ogiltigt system-ID. | The identifier system value must be be from list of valid systems (see section "Parameters (In)" above) | Error |
| revokedBy | 2-XX-5: Parametern %s saknas. | Parameters with cardinality 1..N must be supplied | Error |
| id | 2-XX-6: Fullmakt med id %s hittades inte. | PowerOfAttorney with supplied logical ID not found | Error |
| revokedBy | 2-XX-11: Angiven person är inte behörig att återkalla fullmakten. | revokedBy is not authorized to revoke the PowerOfAttorney. | Error |
| 4-XX-2: Fullmakten har återkallats/återgivits. | PowerOfAttorney revoked successfully. | Success | |
| 4-XX-3: Fullmakten är redan återkallad/återgiven. | PowerOfAttorney was already revoked. | Information |
Examples of requests
Invocation: POST [base]/Consent/442b7631-8503-4b38-83d8-59c4e1ed800c/$revoke
Request body:
| Parameters |
| id : RevokeConsent-CoordinationNumber-RequestBody |
| parameter |
| name : revokedBy |
| value |
| system : http://electronichealth.se/identifier/samordningsnummer |
| value : 201903682399 |
Examples of responses
Successful operation
A successful operation returns an OperationOutcome with issue.severity and issue.code both set to "success".
| OperationOutcome |
| id : ee3dd06b-a6ac-4b3c-ad68-da920cce5271 |
| issue |
| severity : success |
| code : success |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 4-XX-2 |
| display : Fullmakten har återkallats/återgivits. |
Already revoked
If the NDIPowerOfAttorney has already been revoked, the response will be an OperationOutcome with issue.severity set to "information" and issue.code set to "processing".
| OperationOutcome |
| id : 77398b7d-6ff1-425b-ab7c-02fd981a28be |
| issue |
| severity : information |
| code : processing |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 4-XX-3 |
| display : Fullmakten är redan återkallad/återgiven. |
Failed operation
A failed operation returns an OperationOutcome with an issue.severity set to "error".
The following example shows a response when the person with the supplied identifier in parameter revokedBy is unauthorized to revoke a PowerOfAttorney. The response is an OperationOutcome with issue.code set to "forbidden".
| OperationOutcome |
| id : 958f3ae0-d085-48d3-9e95-df5dc2537b42 |
| issue |
| severity : error |
| code : forbidden |
| details |
| coding |
| system : http://electronichealth.se/CodeSystem/error-codes |
| code : 2-XX-11 |
| display : Endast fullmaktsgivare eller fullmaktshavare får återkalla en fullmakt. |