PACIO Advance Directive Interoperability Implementation Guide
1.0.0 - STU 1 United States of America flag

This page is part of the PACIO Advance Directive Information Implementation Guide (v1.0.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Resource Profile: ADI Notary

Official URL: http://hl7.org/fhir/us/pacio-adi/StructureDefinition/ADI-Notary Version: 1.0.0
Active as of 2024-01-11 Computable Name: ADINotary

This profile represents a person participating as a notary for a person’s advance directives.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from RelatedPerson

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... text 1..1NarrativeText summary of the resource, for human interpretation
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... NotaryInformationExtension 0..1(Complex)Notary Information
URL: http://hl7.org/fhir/us/pacio-adi/StructureDefinition/adi-notaryInformation-extension
... patient S1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship S1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary S1..1CodeableConceptThe nature of the relationship
Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
... name S1..1HumanNameA name associated with the person
... telecom S1..*ContactPointA contact detail for the person
... address S0..*AddressAddress where the related person can be contacted or visited

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
RelatedPerson.relationshipextensiblePatientRelationshipType
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 1..1NarrativeText summary of the resource, for human interpretation
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... active ?!SΣ0..1booleanWhether this related person's record is in active use
... patient SΣ1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship SΣ1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary SΣ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.



Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
... name SΣ1..1HumanNameA name associated with the person
... telecom SΣ1..*ContactPointA contact detail for the person
... address SΣ0..*AddressAddress where the related person can be contacted or visited

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.relationshipextensiblePatientRelationshipType
RelatedPerson.relationship:notarypreferredPattern: NOTARY
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 1..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... NotaryInformationExtension C0..1(Complex)Notary Information
URL: http://hl7.org/fhir/us/pacio-adi/StructureDefinition/adi-notaryInformation-extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!SΣ0..1booleanWhether this related person's record is in active use
... patient SΣ1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship SΣ1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary SΣ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.



Required Pattern: At least the following
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
...... display0..1stringRepresentation defined by the system
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text0..1stringPlain text representation of the concept
... name SΣ1..1HumanNameA name associated with the person
... telecom SΣ1..*ContactPointA contact detail for the person
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the related person was born
... address SΣ0..*AddressAddress where the related person can be contacted or visited
... photo 0..*AttachmentImage of the person
... period 0..1PeriodPeriod of time that this relationship is considered valid
... communication 0..*BackboneElementA language which may be used to communicate with about the patient's health
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
RelatedPerson.relationshipextensiblePatientRelationshipType
RelatedPerson.relationship:notarypreferredPattern: NOTARY
RelatedPerson.genderrequiredAdministrativeGender
RelatedPerson.communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding

This structure is derived from RelatedPerson

Summary

Mandatory: 5 elements
Must-Support: 7 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element RelatedPerson.relationship is sliced based on the value of pattern:$this

Differential View

This structure is derived from RelatedPerson

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... text 1..1NarrativeText summary of the resource, for human interpretation
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... NotaryInformationExtension 0..1(Complex)Notary Information
URL: http://hl7.org/fhir/us/pacio-adi/StructureDefinition/adi-notaryInformation-extension
... patient S1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship S1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary S1..1CodeableConceptThe nature of the relationship
Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
... name S1..1HumanNameA name associated with the person
... telecom S1..*ContactPointA contact detail for the person
... address S0..*AddressAddress where the related person can be contacted or visited

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
RelatedPerson.relationshipextensiblePatientRelationshipType

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 1..1NarrativeText summary of the resource, for human interpretation
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... active ?!SΣ0..1booleanWhether this related person's record is in active use
... patient SΣ1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship SΣ1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary SΣ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.



Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
... name SΣ1..1HumanNameA name associated with the person
... telecom SΣ1..*ContactPointA contact detail for the person
... address SΣ0..*AddressAddress where the related person can be contacted or visited

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.relationshipextensiblePatientRelationshipType
RelatedPerson.relationship:notarypreferredPattern: NOTARY

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 1..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... NotaryInformationExtension C0..1(Complex)Notary Information
URL: http://hl7.org/fhir/us/pacio-adi/StructureDefinition/adi-notaryInformation-extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!SΣ0..1booleanWhether this related person's record is in active use
... patient SΣ1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship SΣ1..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: PatientRelationshipType (extensible)
.... relationship:notary SΣ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.



Required Pattern: At least the following
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: NOTARY
...... display0..1stringRepresentation defined by the system
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text0..1stringPlain text representation of the concept
... name SΣ1..1HumanNameA name associated with the person
... telecom SΣ1..*ContactPointA contact detail for the person
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the related person was born
... address SΣ0..*AddressAddress where the related person can be contacted or visited
... photo 0..*AttachmentImage of the person
... period 0..1PeriodPeriod of time that this relationship is considered valid
... communication 0..*BackboneElementA language which may be used to communicate with about the patient's health
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
RelatedPerson.relationshipextensiblePatientRelationshipType
RelatedPerson.relationship:notarypreferredPattern: NOTARY
RelatedPerson.genderrequiredAdministrativeGender
RelatedPerson.communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding

This structure is derived from RelatedPerson

Summary

Mandatory: 5 elements
Must-Support: 7 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element RelatedPerson.relationship is sliced based on the value of pattern:$this

 

Other representations of profile: CSV, Excel, Schematron