DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

5.1.3.3 StructureDefinition: USLabPHPatient

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/patient-uslab-uslabphpatient

Patient with expanded contact information

This profile was published on Mon, Nov 17, 2014 00:00+1100 as a draft by HL7 International - Orders and Observations WG.

5.1.3.3.1 Formal Views of Profile Content

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

This structure is derived from Patient.

Summary

Mandatory: 26 elements, Must-Support: 56 elements, Fixed Value: 2 elements

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element Patient.telecom is sliced based on the value of use

This structure is derived from Patient.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 1..1PatientPatient with expanded contact information
... identifier S1..*
.... use S1..1
.... system S1..1Organization or System URI
.... value S1..1Patient Identifier String
... name S1..*
.... use S1..1codeBinding: USLabPHNameUse (required)
.... family S1..1
.... given S0..2
.... prefix S0..1
.... suffix S0..1
... telecom Slice: Unordered, Open, by use
... telecom S0..*
.... system S1..1
.... value S1..1
.... use S1..1codeFixed Value: home
... telecom S0..*
.... system S1..1
.... value S1..1
.... use S1..1codeFixed Value: work
... gender S1..1
... birthDate S0..1
... deceased[x] S0..1
... address S0..*
.... use S0..1
.... line S0..2
.... city S0..1
.... state S0..1Binding: USPSState (required)
.... postalCode S I0..1US Zip Codes
inv-1: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
.... country S0..1ISO 3166 3 letter Country Code
Binding: USCountry (extensible)
.... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
... contact S0..*
.... relationship S0..1
..... coding S1..1
...... code S1..1
.... name S0..*
..... family S1..1
..... given S0..2
..... suffix S0..1
.... telecom S0..3
..... system S1..1
..... value S1..1
.... address S0..*
..... use S1..1
..... line S0..2
..... city S0..1
..... state S0..1Binding: USPSState (required)
..... postalCode S I0..1US Zip Codes
inv-2: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
..... country S0..1ISO 3166 3 letter Country Code
Binding: USCountry (extensible)
..... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
... us-core-race S0..*CodeableConceptA category of humans sharing history, origin or nationality
Binding: DAFRace (required)
.... coding S1..1
..... system S1..1
..... code S1..1
... us-core-ethnicity S0..1CodeableConceptA category of human sharing heritage
Binding: DAFEthnicity (required)
.... coding S1..1
..... system S1..1
..... code S1..1
NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 1..1PatientPatient with expanded contact information
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... us-core-race S0..*CodeableConceptExtension
Binding: DAFRace (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... url 1..1uriidentifies the meaning of the extension
.... value[x] 0..1*Value of extension
... us-core-ethnicity S0..1CodeableConceptExtension
Binding: DAFEthnicity (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... url 1..1uriidentifies the meaning of the extension
.... value[x] 0..1*Value of extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S Σ1..*IdentifierAn identifier for this patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S1..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type 0..1CodeableConceptDescription of identifier
Binding: IdentifierType (extensible)
.... system S1..1uriOrganization or System URI
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the id itself is a full uri
.... value S1..1stringPatient Identifier String
Example: 123456
.... period 0..1PeriodTime period when id is/was valid for use
.... assigner 0..1OrganizationOrganization that issued id (may be just text)
... name S Σ1..*HumanNameA name associated with the patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: USLabPHNameUse (required)
.... text 0..1stringText representation of the full name
.... family S1..1stringFamily name (often called 'Surname')
.... given S0..2stringGiven names (not always 'first'). Includes middle names
.... prefix S0..1stringParts that come before the name
.... suffix S0..1stringParts that come after the name
.... period 0..1PeriodTime period when name was/is in use
... telecom ΣContactPointA contact detail for the individual
Slice: Unordered, Open, by use
... telecom S Σ0..*ContactPointA contact detail for the individual
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
.... value S1..1stringThe actual contact point details
.... use ?! S1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
Fixed Value: home
.... period 0..1PeriodTime period when the contact point was/is in use
... telecom S Σ0..*ContactPointA contact detail for the individual
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
.... value S1..1stringThe actual contact point details
.... use ?! S1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
Fixed Value: work
.... period 0..1PeriodTime period when the contact point was/is in use
... gender S Σ1..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate S Σ0..1dateThe date of birth for the individual
... deceased[x] ?! SΣ0..1boolean, dateTimeIndicates if the individual is deceased or not
... address S Σ0..*AddressAddresses for the individual
.... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
.... use ?! S0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... text 0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line S0..2stringStreet name, number, direction & P.O. Box etc
Example: 137 Nowhere Street
.... city S0..1stringName of city, town etc.
Example: Erewhon
.... state S0..1stringSub-unit of country (abreviations ok)
Binding: USPSState (required)
.... postalCode S I0..1stringUS Zip Codes
inv-1: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
.... country S0..1stringISO 3166 3 letter Country Code
Binding: USCountry (extensible)
.... period 0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... maritalStatus 0..1CodeableConceptMarital (civil) status of a patient
Binding: MaritalStatus (required)
... multipleBirth[x] 0..1boolean, integerWhether patient is part of a multiple birth
... photo 0..*AttachmentImage of the patient
... contact S I0..*A contact party (e.g. guardian, partner, friend) for the patient
pat-1: SHALL at least contain a contact's details or a reference to an organization
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... relationship S0..1CodeableConceptThe kind of relationship
Binding: ContactRelationship (required)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S1..1CodingCode defined by a terminology system
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system 0..1uriIdentity of the terminology system
...... version 0..1stringVersion of the system - if relevant
...... code S1..1codeSymbol in syntax defined by the system
...... display 0..1stringRepresentation defined by the system
...... primary 0..1booleanIf this code was chosen directly by the user
..... text 0..1stringPlain text representation of the concept
.... name S0..*HumanNameA name associated with the contact person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... use ?!0..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
..... text 0..1stringText representation of the full name
..... family S1..1stringFamily name (often called 'Surname')
..... given S0..2stringGiven names (not always 'first'). Includes middle names
..... prefix 0..*stringParts that come before the name
..... suffix S0..1stringParts that come after the name
..... period 0..1PeriodTime period when name was/is in use
.... telecom S0..3ContactPointA contact detail for the person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
..... value S1..1stringThe actual contact point details
..... use ?!0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... period 0..1PeriodTime period when the contact point was/is in use
.... address S0..*AddressAddress for the contact person
..... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
..... use ?! S1..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
..... text 0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
..... line S0..2stringStreet name, number, direction & P.O. Box etc
Example: 137 Nowhere Street
..... city S0..1stringName of city, town etc.
Example: Erewhon
..... state S0..1stringSub-unit of country (abreviations ok)
Binding: USPSState (required)
..... postalCode S I0..1stringUS Zip Codes
inv-2: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
..... country S0..1stringISO 3166 3 letter Country Code
Binding: USCountry (extensible)
..... period 0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
.... gender 0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
.... organization I0..1OrganizationOrganization that is associated with the contact
.... period 0..1PeriodThe period during which this contact person or organization is valid to be contacted relating to this patient
... animal ?! Σ0..1If this patient is an animal (non-human)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... species Σ1..1CodeableConceptE.g. Dog, Cow
Binding: AnimalSpecies (example)
.... breed Σ0..1CodeableConceptE.g. Poodle, Angus
Binding: AnimalBreed (example)
.... genderStatus Σ0..1CodeableConceptE.g. Neutered, Intact
Binding: AnimalGenderStatus (example)
... communication 0..*A list of Languages which may be used to communicate with the patient about his or her health
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: Language (required)
.... preferred 0..1booleanLanguage preference indicator
... careProvider 0..*Organization, PractitionerPatient's nominated care provider
... managingOrganization Σ0..1OrganizationOrganization that is the custodian of the patient record
... link ?!0..*Link to another patient resource that concerns the same actual person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... other ?!1..1PatientThe other patient resource that the link refers to
.... type ?!1..1codereplace | refer | seealso - type of link
Binding: LinkType (required)
... active ?! Σ0..1booleanWhether this patient's record is in active use

todo

This structure is derived from Patient.

Summary

Mandatory: 26 elements, Must-Support: 56 elements, Fixed Value: 2 elements

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element Patient.telecom is sliced based on the value of use

Differential View

This structure is derived from Patient.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 1..1PatientPatient with expanded contact information
... identifier S1..*
.... use S1..1
.... system S1..1Organization or System URI
.... value S1..1Patient Identifier String
... name S1..*
.... use S1..1codeBinding: USLabPHNameUse (required)
.... family S1..1
.... given S0..2
.... prefix S0..1
.... suffix S0..1
... telecom Slice: Unordered, Open, by use
... telecom S0..*
.... system S1..1
.... value S1..1
.... use S1..1codeFixed Value: home
... telecom S0..*
.... system S1..1
.... value S1..1
.... use S1..1codeFixed Value: work
... gender S1..1
... birthDate S0..1
... deceased[x] S0..1
... address S0..*
.... use S0..1
.... line S0..2
.... city S0..1
.... state S0..1Binding: USPSState (required)
.... postalCode S I0..1US Zip Codes
inv-1: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
.... country S0..1ISO 3166 3 letter Country Code
Binding: USCountry (extensible)
.... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
... contact S0..*
.... relationship S0..1
..... coding S1..1
...... code S1..1
.... name S0..*
..... family S1..1
..... given S0..2
..... suffix S0..1
.... telecom S0..3
..... system S1..1
..... value S1..1
.... address S0..*
..... use S1..1
..... line S0..2
..... city S0..1
..... state S0..1Binding: USPSState (required)
..... postalCode S I0..1US Zip Codes
inv-2: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
..... country S0..1ISO 3166 3 letter Country Code
Binding: USCountry (extensible)
..... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
... us-core-race S0..*CodeableConceptA category of humans sharing history, origin or nationality
Binding: DAFRace (required)
.... coding S1..1
..... system S1..1
..... code S1..1
... us-core-ethnicity S0..1CodeableConceptA category of human sharing heritage
Binding: DAFEthnicity (required)
.... coding S1..1
..... system S1..1
..... code S1..1

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Patient 1..1PatientPatient with expanded contact information
... meta 0..1MetaMetadata about the resource
... implicitRules ?!0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: Language (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... us-core-race S0..*CodeableConceptExtension
Binding: DAFRace (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... url 1..1uriidentifies the meaning of the extension
.... value[x] 0..1*Value of extension
... us-core-ethnicity S0..1CodeableConceptExtension
Binding: DAFEthnicity (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... url 1..1uriidentifies the meaning of the extension
.... value[x] 0..1*Value of extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S Σ1..*IdentifierAn identifier for this patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S1..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
.... type 0..1CodeableConceptDescription of identifier
Binding: IdentifierType (extensible)
.... system S1..1uriOrganization or System URI
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the id itself is a full uri
.... value S1..1stringPatient Identifier String
Example: 123456
.... period 0..1PeriodTime period when id is/was valid for use
.... assigner 0..1OrganizationOrganization that issued id (may be just text)
... name S Σ1..*HumanNameA name associated with the patient
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: USLabPHNameUse (required)
.... text 0..1stringText representation of the full name
.... family S1..1stringFamily name (often called 'Surname')
.... given S0..2stringGiven names (not always 'first'). Includes middle names
.... prefix S0..1stringParts that come before the name
.... suffix S0..1stringParts that come after the name
.... period 0..1PeriodTime period when name was/is in use
... telecom ΣContactPointA contact detail for the individual
Slice: Unordered, Open, by use
... telecom S Σ0..*ContactPointA contact detail for the individual
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
.... value S1..1stringThe actual contact point details
.... use ?! S1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
Fixed Value: home
.... period 0..1PeriodTime period when the contact point was/is in use
... telecom S Σ0..*ContactPointA contact detail for the individual
.... extension 0..*ExtensionAdditional Content defined by implementations
.... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
.... value S1..1stringThe actual contact point details
.... use ?! S1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
Fixed Value: work
.... period 0..1PeriodTime period when the contact point was/is in use
... gender S Σ1..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
... birthDate S Σ0..1dateThe date of birth for the individual
... deceased[x] ?! SΣ0..1boolean, dateTimeIndicates if the individual is deceased or not
... address S Σ0..*AddressAddresses for the individual
.... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
.... use ?! S0..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
.... text 0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
.... line S0..2stringStreet name, number, direction & P.O. Box etc
Example: 137 Nowhere Street
.... city S0..1stringName of city, town etc.
Example: Erewhon
.... state S0..1stringSub-unit of country (abreviations ok)
Binding: USPSState (required)
.... postalCode S I0..1stringUS Zip Codes
inv-1: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
.... country S0..1stringISO 3166 3 letter Country Code
Binding: USCountry (extensible)
.... period 0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
... maritalStatus 0..1CodeableConceptMarital (civil) status of a patient
Binding: MaritalStatus (required)
... multipleBirth[x] 0..1boolean, integerWhether patient is part of a multiple birth
... photo 0..*AttachmentImage of the patient
... contact S I0..*A contact party (e.g. guardian, partner, friend) for the patient
pat-1: SHALL at least contain a contact's details or a reference to an organization
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... relationship S0..1CodeableConceptThe kind of relationship
Binding: ContactRelationship (required)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S1..1CodingCode defined by a terminology system
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system 0..1uriIdentity of the terminology system
...... version 0..1stringVersion of the system - if relevant
...... code S1..1codeSymbol in syntax defined by the system
...... display 0..1stringRepresentation defined by the system
...... primary 0..1booleanIf this code was chosen directly by the user
..... text 0..1stringPlain text representation of the concept
.... name S0..*HumanNameA name associated with the contact person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... use ?!0..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
..... text 0..1stringText representation of the full name
..... family S1..1stringFamily name (often called 'Surname')
..... given S0..2stringGiven names (not always 'first'). Includes middle names
..... prefix 0..*stringParts that come before the name
..... suffix S0..1stringParts that come after the name
..... period 0..1PeriodTime period when name was/is in use
.... telecom S0..3ContactPointA contact detail for the person
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S I1..1codephone | fax | email | url
Binding: ContactPointSystem (required)
..... value S1..1stringThe actual contact point details
..... use ?!0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... period 0..1PeriodTime period when the contact point was/is in use
.... address S0..*AddressAddress for the contact person
..... us-core-county S0..1stringCounty/Parish FIPS codes
Binding: USFIPSCounty (required)
..... use ?! S1..1codehome | work | temp | old - purpose of this address
Binding: AddressUse (required)
Example: home
..... text 0..1stringText representation of the address
Example: 137 Nowhere Street, Erewhon 9132
..... line S0..2stringStreet name, number, direction & P.O. Box etc
Example: 137 Nowhere Street
..... city S0..1stringName of city, town etc.
Example: Erewhon
..... state S0..1stringSub-unit of country (abreviations ok)
Binding: USPSState (required)
..... postalCode S I0..1stringUS Zip Codes
inv-2: (Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
Example: 9132
..... country S0..1stringISO 3166 3 letter Country Code
Binding: USCountry (extensible)
..... period 0..1PeriodTime period when address was/is in use
Example: {"start":"2010-03-23","end":"2010-07-01"}
.... gender 0..1codemale | female | other | unknown
Binding: AdministrativeGender (required)
.... organization I0..1OrganizationOrganization that is associated with the contact
.... period 0..1PeriodThe period during which this contact person or organization is valid to be contacted relating to this patient
... animal ?! Σ0..1If this patient is an animal (non-human)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... species Σ1..1CodeableConceptE.g. Dog, Cow
Binding: AnimalSpecies (example)
.... breed Σ0..1CodeableConceptE.g. Poodle, Angus
Binding: AnimalBreed (example)
.... genderStatus Σ0..1CodeableConceptE.g. Neutered, Intact
Binding: AnimalGenderStatus (example)
... communication 0..*A list of Languages which may be used to communicate with the patient about his or her health
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: Language (required)
.... preferred 0..1booleanLanguage preference indicator
... careProvider 0..*Organization, PractitionerPatient's nominated care provider
... managingOrganization Σ0..1OrganizationOrganization that is the custodian of the patient record
... link ?!0..*Link to another patient resource that concerns the same actual person
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... other ?!1..1PatientThe other patient resource that the link refers to
.... type ?!1..1codereplace | refer | seealso - type of link
Binding: LinkType (required)
... active ?! Σ0..1booleanWhether this patient's record is in active use

XML Template

JSON Template

todo

 

Other representations of profile: (todo)

5.1.3.3.2 Terminology Bindings

PathNameConformanceValueSet
Patient.languageLanguagerequiredhttp://tools.ietf.org/html/bcp47
Patient.extension
http://hl7.org/fhir/StructureDefinition/us-core-race		DAFRacerequiredMU Race Value Set
Patient.extension
http://hl7.org/fhir/StructureDefinition/us-core-ethnicity		DAFEthnicityrequiredEthnicity group
Patient.identifier.useIdentifierUserequiredIdentifierUse
Patient.identifier.typeIdentifierTypeextensibleIdentifier Type Codes
Patient.name.useUSLabPHNameUserequiredUSLabPHNameUse
Patient.telecom.systemContactPointSystemrequiredContactPointSystem
Patient.telecom.useContactPointUserequiredContactPointUse
Patient.telecom.systemContactPointSystemrequiredContactPointSystem
Patient.telecom.useContactPointUserequiredContactPointUse
Patient.genderAdministrativeGenderrequiredAdministrativeGender
Patient.address.extension
http://hl7.org/fhir/StructureDefinition/us-core-county		USFIPSCountyrequiredUS counties and county equivalent entities codes
Patient.address.useAddressUserequiredAddressUse
Patient.address.stateUSPSStaterequiredUSPS Two Letter Alphabetic Codes
Patient.address.countryUSCountryextensiblehttp://www.iso.org/iso/country_codes.htm
Patient.maritalStatusMaritalStatusrequiredMarital Status Codes
Patient.contact.relationshipContactRelationshiprequiredPatientContactRelationship
Patient.contact.name.useNameUserequiredNameUse
Patient.contact.telecom.systemContactPointSystemrequiredContactPointSystem
Patient.contact.telecom.useContactPointUserequiredContactPointUse
Patient.contact.address.extension
http://hl7.org/fhir/StructureDefinition/us-core-county		USFIPSCountyrequiredUS counties and county equivalent entities codes
Patient.contact.address.useAddressUserequiredAddressUse
Patient.contact.address.stateUSPSStaterequiredUSPS Two Letter Alphabetic Codes
Patient.contact.address.countryUSCountryextensiblehttp://www.iso.org/iso/country_codes.htm
Patient.contact.genderAdministrativeGenderrequiredAdministrativeGender
Patient.animal.speciesAnimalSpeciesexampleAnimalSpecies
Patient.animal.breedAnimalBreedexampleAnimalBreeds
Patient.animal.genderStatusAnimalGenderStatusexampleGenderStatus
Patient.communication.languageLanguagerequiredhttp://tools.ietf.org/html/bcp47
Patient.link.typeLinkTyperequiredLinkType

5.1.3.3.3 Constraints

IdPathNameDetails
inv-1Patient.address.postalCodeRegex for Zip(Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
XPath: f:matches(issued,[0-9]{5}(-[0-9]{4}){0,1} )
pat-1Patient.contactContactNeedsDetailsSHALL at least contain a contact's details or a reference to an organization
XPath: f:name or f:telecom or f:address or f:organization
inv-2Patient.contact.address.postalCodeRegex for Zip(Zip or Postal Code) SHALL be formatted as 99999[-9999] for US Zip or ZIP +4 codes or as A9A9A9 for Canadian postal codes.
XPath: f:matches(issued,[0-9]{5}(-[0-9]{4}){0,1} )
.