PACIO Advance Directive Interoperability Implementation Guide
0.1.0 - STU 1 Ballot

This page is part of the PACIO Advance Directive Information Implementation Guide (v0.1.0: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Resource Profile: ADI Participant

Defining URL:http://hl7.org/fhir/us/pacio-adi/StructureDefinition/PADI-Participant
Version:0.1.0
Name:PADIParticipant
Title:ADI Participant
Status:Active as of 12/6/21 8:50 PM
Definition:

This profile represents a person participating in a persons advance directives in some capacity such as healthcare agent or healthcare agent advisor.

Publisher:HL7 Patient Empowerment Working Group
Source Resource:XML / JSON / Turtle

The official URL for this profile is: 

http://hl7.org/fhir/us/pacio-adi/StructureDefinition/PADI-Participant

Formal Views of Profile Content

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

This structure is derived from RelatedPerson

Summary

Mandatory: 3 elements (2 nested mandatory elements)
Must-Support: 3 elements

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

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

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
... patient S1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship S0..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: Participant Relationships (extensible)
.... relationship:personal_and_legal_relationship_role S0..1CodeableConceptThe nature of the relationship
Binding: Personal And Legal Relationship Role Type (required)
..... coding 1..1CodingCode defined by a terminology system
...... display 1..1stringRepresentation defined by the system
... telecom 1..*ContactPointA contact detail for the person

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... id Σ0..1stringLogical 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
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!Σ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Σ0..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: Participant Relationships (extensible)
.... relationship:personal_and_legal_relationship_role SΣ0..1CodeableConceptThe nature of the relationship
Binding: Personal And Legal Relationship Role Type (required)
..... id 0..1stringUnique id for inter-element referencing
..... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding Σ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ0..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ0..1codeSymbol in syntax defined by the system
...... display Σ1..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... name Σ1..1HumanNameA name associated with the person
... telecom Σ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 Σ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)
Max Binding: AllLanguages: A human language.

.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... patient Σ1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship Σ0..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: Participant Relationships (extensible)
.... relationship:personal_and_legal_relationship_role Σ0..1CodeableConceptThe nature of the relationship
Binding: Personal And Legal Relationship Role Type (required)

doco Documentation for this format

This structure is derived from RelatedPerson

Summary

Mandatory: 3 elements (2 nested mandatory elements)
Must-Support: 3 elements

Structures

This structure refers to these other structures:

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
... patient S1..1Reference(US Core Patient Profile)The patient this person is related to
... Slices for relationship S0..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: Participant Relationships (extensible)
.... relationship:personal_and_legal_relationship_role S0..1CodeableConceptThe nature of the relationship
Binding: Personal And Legal Relationship Role Type (required)
..... coding 1..1CodingCode defined by a terminology system
...... display 1..1stringRepresentation defined by the system
... telecom 1..*ContactPointA contact detail for the person

doco Documentation for this format

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..1stringLogical 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
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!Σ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Σ0..*CodeableConceptThe nature of the relationship
Slice: Unordered, Open by pattern:$this
Binding: Participant Relationships (extensible)
.... relationship:personal_and_legal_relationship_role SΣ0..1CodeableConceptThe nature of the relationship
Binding: Personal And Legal Relationship Role Type (required)
..... id 0..1stringUnique id for inter-element referencing
..... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... coding Σ1..1CodingCode defined by a terminology system
...... id 0..1stringUnique id for inter-element referencing
...... Slices for extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ0..1uriIdentity of the terminology system
...... version Σ0..1stringVersion of the system - if relevant
...... code Σ0..1codeSymbol in syntax defined by the system
...... display Σ1..1stringRepresentation defined by the system
...... userSelected Σ0..1booleanIf this coding was chosen directly by the user
..... text Σ0..1stringPlain text representation of the concept
... name Σ1..1HumanNameA name associated with the person
... telecom Σ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 Σ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)
Max Binding: AllLanguages: A human language.

.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

 

Other representations of profile: CSV, Excel, Schematron

Terminology Bindings

PathConformanceValueSet
RelatedPerson.languagepreferredCommonLanguages
Max Binding: AllLanguages
RelatedPerson.relationshipextensiblePADIParticipantRelationshipVS
RelatedPerson.relationship:personal_and_legal_relationship_rolerequiredPADIPersonalAndLegalRelationshipRoleTypeVS
RelatedPerson.genderrequiredAdministrativeGender
RelatedPerson.communication.languagepreferredCommonLanguages
Max Binding: AllLanguages