International Patient Summary IG

Patient

Minimum expectations for the Patient resource when used in the IPS composition or in the referred resources.

Tree view

Patient-uv-ips (Patient)			http://hl7.org/fhir/StructureDefinition/Patient	There are no (further) constraints on this element Data type http://hl7.org/fhir/StructureDefinition/Patient
name	S			There are no (further) constraints on this element Element id Patient.name Requirements Need to be able to track the patient by multiple names. Examples are your official name and a partner name. The Alphabetic representation of the name SHALL be always provided
family	S	1..		There are no (further) constraints on this element Element id Patient.name.family
given	S	1..1		There are no (further) constraints on this element Element id Patient.name.given
telecom	S			There are no (further) constraints on this element Element id Patient.telecom
gender	S	1..		There are no (further) constraints on this element Element id Patient.gender
birthDate	S	1..		There are no (further) constraints on this element Element id Patient.birthDate
address	S			There are no (further) constraints on this element Element id Patient.address
line	S			There are no (further) constraints on this element Element id Patient.address.line
city	S			There are no (further) constraints on this element Element id Patient.address.city
state	S			There are no (further) constraints on this element Element id Patient.address.state
postalCode	S			There are no (further) constraints on this element Element id Patient.address.postalCode
country	S			There are no (further) constraints on this element Element id Patient.address.country Comments ISO 3166 3 letter codes can be used in place of a full country name. Required for cross-border exchange of IPS
contact	S			There are no (further) constraints on this element Element id Patient.contact
relationship	S		Codeable ConceptBinding	There are no (further) constraints on this element Element id Patient.contact.relationship Data type Codeable Concept Binding IPSPersonalRelationship (required)
name	S			There are no (further) constraints on this element Element id Patient.contact.name
family	S			There are no (further) constraints on this element Element id Patient.contact.name.family
given	S			There are no (further) constraints on this element Element id Patient.contact.name.given
telecom	S			There are no (further) constraints on this element Element id Patient.contact.telecom
address	S			There are no (further) constraints on this element Element id Patient.contact.address
line	S			There are no (further) constraints on this element Element id Patient.contact.address.line
city	S			There are no (further) constraints on this element Element id Patient.contact.address.city
state	S			There are no (further) constraints on this element Element id Patient.contact.address.state
country	S			There are no (further) constraints on this element Element id Patient.contact.address.country
organization	S			There are no (further) constraints on this element Element id Patient.contact.organization
identifier		..0		There are no (further) constraints on this element Element id Patient.contact.organization.identifier
animal		..0		There are no (further) constraints on this element Element id Patient.animal
communication	S			There are no (further) constraints on this element Element id Patient.communication
language	S			There are no (further) constraints on this element Element id Patient.communication.language
generalPractitioner	S			There are no (further) constraints on this element Element id Patient.generalPractitioner
identifier		..0		There are no (further) constraints on this element Element id Patient.generalPractitioner.identifier


Patient.name
Must Support	True
Requirements	Need to be able to track the patient by multiple names. Examples are your official name and a partner name. The Alphabetic representation of the name SHALL be always provided
Patient.name.family
Cardinality	1
Must Support	True
Patient.name.given
Cardinality	1..1
Must Support	True
Patient.telecom
Must Support	True
Patient.gender
Cardinality	1
Must Support	True
Patient.birthDate
Cardinality	1
Must Support	True
Patient.address
Must Support	True
Patient.address.line
Must Support	True
Patient.address.city
Must Support	True
Patient.address.state
Must Support	True
Patient.address.postalCode
Must Support	True
Patient.address.country
Must Support	True
Comments	ISO 3166 3 letter codes can be used in place of a full country name. Required for cross-border exchange of IPS
Patient.contact
Must Support	True
Patient.contact.relationship
Type	Codeable Concept
Binding	IPSPersonalRelationship (required)
Must Support	True
Patient.contact.name
Must Support	True
Patient.contact.name.family
Must Support	True
Patient.contact.name.given
Must Support	True
Patient.contact.telecom
Must Support	True
Patient.contact.address
Must Support	True
Patient.contact.address.line
Must Support	True
Patient.contact.address.city
Must Support	True
Patient.contact.address.state
Must Support	True
Patient.contact.address.country
Must Support	True
Patient.contact.organization
Must Support	True
Patient.contact.organization.identifier
Cardinality	..0
Patient.animal
Cardinality	..0
Patient.communication
Must Support	True
Patient.communication.language
Must Support	True
Patient.generalPractitioner
Must Support	True
Patient.generalPractitioner.identifier
Cardinality	..0