Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient vs http://hl7.org/fhir/us/insurance-card/StructureDefinition/C4DIC-Patient

Left:US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)
Right:C4DIC Patient (http://hl7.org/fhir/us/insurance-card/StructureDefinition/C4DIC-Patient)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient' vs 'http://hl7.org/fhir/us/insurance-card/StructureDefinition/C4DIC-Patient'
ErrorStructureDefinition.versionValues for version differ: '5.0.1' vs '1.0.0'
InformationStructureDefinition.nameValues for name differ: 'USCorePatientProfile' vs 'C4DICPatient'
InformationStructureDefinition.titleValues for title differ: 'US Core Patient Profile' vs 'C4DIC Patient'
InformationStructureDefinition.dateValues for date differ: '2022-04-20T15:02:49-07:00' vs '2022-07-13T17:22:13+00:00'
InformationStructureDefinition.publisherValues for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 Payer/Provider Information Exchange Working Group (PIE WG)'
WarningPatientElements differ in short: 'Information about an individual or animal receiving health care services' vs 'Information about an individual who has health insurance coverage'
WarningPatientElements differ in definition: '\-' vs 'Demographics and other administrative information about an individual with insurance coverage provided by a health plan.'
WarningPatient.metaElements differ in definition for mustSupport: 'false' vs 'true'
InformationPatient.metaElement minimum cardinalities differ: '0' vs '1'
WarningPatient.meta.lastUpdatedElements differ in comments: 'This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read] interaction.' vs 'Defines the date the Resource was created or updated, whichever comes last. Payers SHALL provide the last time the data was updated or the date of creation in the payer’s system of record, whichever comes last.'
WarningPatient.meta.lastUpdatedElements differ in definition for mustSupport: 'false' vs 'true'
InformationPatient.meta.lastUpdatedElement minimum cardinalities differ: '0' vs '1'
WarningPatient.meta.profileElements differ in comments: 'It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.' vs 'meta.profile is required as a matter of convenience of receiving systems. The meta.profile should be used by the Server to hint/assert/declare that this instance conforms to one (or more) stated profiles (with business versions). meta.profile does not capture any business logic, processing directives, or semantics (for example, inpatient or outpatient). Clients should not assume that the Server will exhaustively indicate all profiles with all versions that this instance conforms to. Clients can (and should) perform their own validation of conformance to the indicated profile(s) and to any other profiles of interest.'
InformationPatient.meta.profileElement minimum cardinalities differ: '0' vs '1'
WarningPatient.extensionElements differ in short: 'Extension' vs 'Additional content defined by implementations'
WarningPatient.extensionElements differ in definition: 'An Extension' vs '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 manageable, 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.'
WarningPatient.identifierElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.identifierElement minimum cardinalities differ: '1' vs '0'
WarningPatient.identifier.systemElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.identifier.systemElement minimum cardinalities differ: '1' vs '0'
WarningPatient.identifier.valueElements differ in short: 'The value that is unique within the system.' vs 'The value that is unique'
WarningPatient.identifier.valueElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.identifier.valueElement minimum cardinalities differ: '1' vs '0'
InformationPatient.nameElement maximum cardinalities differ: '2147483647' vs '1'
WarningPatient.name.familyElements differ in comments: 'Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).' vs 'Where an individual has only one name, payers SHALL provide the information as family name to ensure consistency.'
InformationPatient.name.familyElement minimum cardinalities differ: '0' vs '1'
WarningPatient.telecom.systemElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.telecom.systemElement minimum cardinalities differ: '1' vs '0'
WarningPatient.telecom.valueElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.telecom.valueElement minimum cardinalities differ: '1' vs '0'
WarningPatient.telecom.useElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.genderElements differ in comments: 'The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a 'hard' error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.' vs 'MAY be excluded. Gender is not a data element typically found on physical insurance cards. Furthermore, self-identified gender may change over time. Including this element could create a situation where the gender element in the provided resource does not match that in another form of identification or does not match the member's self-identified gender.'
WarningPatient.genderElements differ in definition for mustSupport: 'true' vs 'false'
InformationPatient.genderElement minimum cardinalities differ: '1' vs '0'
WarningPatient.birthDateElements differ in comments: 'At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension 'patient-birthTime' available that should be used where Time is required (such as in maternity/infant care systems).' vs 'MAY be excluded. This data element is printed on some physical insurance cards, but not all.'
WarningPatient.birthDateElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.addressElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.address.lineElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.address.cityElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.address.stateElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.address.postalCodeElements differ in short: 'US Zip Codes' vs 'Postal code for area'
WarningPatient.address.postalCodeElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.address.periodElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.communication.languageElements differ in definition for mustSupport: 'true' vs 'false'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Patient
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2022-04-20T15:02:49-07:002022-07-13T17:22:13+00:00
      • Values Differ
      .descriptionThe US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v2 'Patient Demographics' requirements. This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It identifies which core elements, extensions, vocabularies and value sets **SHALL** be present in the resource when using this profile to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific uses cases.The goal of this profile is to describe a data-minimized version of Patient used to convey information about the Member who has health insurance coverage. Information that would normally not appear on a health insurance card is not required. The use of this profile is only approved for conveying information related to a health insurance card as part of this IG.
      • Values Differ
      .experimentalfalse
      • Removed the item 'false'
      .fhirVersion4.0.1
        .jurisdiction
          ..jurisdiction[0]urn:iso:std:iso:3166#US
            .kindresource
              .nameUSCorePatientProfileC4DICPatient
              • Values Differ
              .publisherHL7 International - Cross-Group ProjectsHL7 Payer/Provider Information Exchange Working Group (PIE WG)
              • Values Differ
              .purpose
                .statusactive
                  .titleUS Core Patient ProfileC4DIC Patient
                  • Values Differ
                  .typePatient
                    .urlhttp://hl7.org/fhir/us/core/StructureDefinition/us-core-patienthttp://hl7.org/fhir/us/insurance-card/StructureDefinition/C4DIC-Patient
                    • Values Differ
                    .version5.0.11.0.0
                    • Values Differ

                    Structure

                    NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                    .. Patient I0..*PatientInformation about an individual or animal receiving health care services
                    us-core-6: Either Patient.name.given and/or Patient.name.family SHALL be present or a Data Absent Reason Extension SHALL be present.
                    0..*PatientInformation about an individual who has health insurance coverage
                    • Elements differ in short: 'Information about an individual or animal receiving health care services' vs 'Information about an individual who has health insurance coverage'
                    • Elements differ in definition: '\-' vs 'Demographics and other administrative information about an individual with insurance coverage provided by a health plan.'
                    ... id Σ0..1stringLogical id of this artifactΣ0..1stringLogical id of this artifact
                      ... meta Σ0..1MetaMetadata about the resourceSΣ1..1MetaMetadata about the resource
                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                      • Element minimum cardinalities differ: '0' vs '1'
                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                        .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                        Slice: Unordered, Open by value:url
                        0..*ExtensionAdditional content defined by implementations
                        Slice: Unordered, Open by value:url
                          .... versionId Σ0..1idVersion specific identifierΣ0..1idVersion specific identifier
                            .... lastUpdated Σ0..1instantWhen the resource version last changedSΣ1..1instantWhen the resource version last changed
                            • Elements differ in comments: 'This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read] interaction.' vs 'Defines the date the Resource was created or updated, whichever comes last. Payers SHALL provide the last time the data was updated or the date of creation in the payer’s system of record, whichever comes last.'
                            • Elements differ in definition for mustSupport: 'false' vs 'true'
                            • Element minimum cardinalities differ: '0' vs '1'
                            .... source Σ0..1uriIdentifies where the resource comes fromΣ0..1uriIdentifies where the resource comes from
                              .... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
                              Σ1..*canonical(StructureDefinition)Profiles this resource claims to conform to
                              Slice: Unordered, Open by pattern:$this
                              • Elements differ in comments: 'It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.' vs 'meta.profile is required as a matter of convenience of receiving systems. The meta.profile should be used by the Server to hint/assert/declare that this instance conforms to one (or more) stated profiles (with business versions). meta.profile does not capture any business logic, processing directives, or semantics (for example, inpatient or outpatient). Clients should not assume that the Server will exhaustively indicate all profiles with all versions that this instance conforms to. Clients can (and should) perform their own validation of conformance to the indicated profile(s) and to any other profiles of interest.'
                              • Element minimum cardinalities differ: '0' vs '1'
                              .... security Σ0..*CodingSecurity Labels applied to this resource
                              Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


                              Σ0..*CodingSecurity Labels applied to this resource
                              Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.


                                .... tag Σ0..*CodingTags applied to this resource
                                Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


                                Σ0..*CodingTags applied to this resource
                                Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".


                                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                    ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                      ... contained 0..*ResourceContained, inline Resources
                                      0..*ResourceContained, inline Resources
                                        ... Slices for extension 0..*ExtensionExtension
                                        Slice: Unordered, Open by value:url
                                        0..*ExtensionAdditional content defined by implementations
                                        • Elements differ in short: 'Extension' vs 'Additional content defined by implementations'
                                        • Elements differ in definition: 'An Extension' vs '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 manageable, 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.'
                                        ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                        ?!0..*ExtensionExtensions that cannot be ignored
                                          ... identifier SΣ1..*IdentifierAn identifier for this patient
                                          Σ0..*IdentifierAn identifier for this patient
                                          • Elements differ in definition for mustSupport: 'true' vs 'false'
                                          • Element minimum cardinalities differ: '1' vs '0'
                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                            Slice: Unordered, Open by value:url
                                            0..*ExtensionAdditional content defined by implementations
                                            Slice: Unordered, Open by value:url
                                              .... use ?!Σ0..1codeusual | official | temp | secondary | old (If known)
                                              Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

                                              ?!Σ0..1codeusual | official | temp | secondary | old (If known)
                                              Binding: IdentifierUse (required): Identifies the purpose for this identifier, if known .

                                                .... type Σ0..1CodeableConceptDescription of identifier
                                                Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

                                                Σ0..1CodeableConceptDescription of identifier
                                                Binding: Identifier Type Codes (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

                                                  .... system SΣ1..1uriThe namespace for the identifier value
                                                  Example General: http://www.acme.com/identifiers/patient
                                                  Σ0..1uriThe namespace for the identifier value
                                                  Example General: http://www.acme.com/identifiers/patient
                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                  .... value SΣ1..1stringThe value that is unique within the system.
                                                  Example General: 123456
                                                  Σ0..1stringThe value that is unique
                                                  Example General: 123456
                                                  • Elements differ in short: 'The value that is unique within the system.' vs 'The value that is unique'
                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                  .... period Σ0..1PeriodTime period when id is/was valid for useΣ0..1PeriodTime period when id is/was valid for use
                                                    .... assigner Σ0..1Reference(Organization)Organization that issued id (may be just text)Σ0..1Reference(Organization)Organization that issued id (may be just text)
                                                      ... active ?!Σ0..1booleanWhether this patient's record is in active use?!Σ0..1booleanWhether this patient's record is in active use
                                                        ... name SΣ1..*HumanNameA name associated with the patient
                                                        SΣ1..1HumanNameA name associated with the patient
                                                        • Element maximum cardinalities differ: '2147483647' vs '1'
                                                        .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                          .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                          Slice: Unordered, Open by value:url
                                                          0..*ExtensionAdditional content defined by implementations
                                                          Slice: Unordered, Open by value:url
                                                            .... use ?!Σ0..1codeusual | official | temp | nickname | anonymous | old | maiden
                                                            Binding: NameUse (required): The use of a human name.

                                                            ?!Σ0..1codeusual | official | temp | nickname | anonymous | old | maiden
                                                            Binding: NameUse (required): The use of a human name.

                                                              .... text Σ0..1stringText representation of the full nameΣ0..1stringText representation of the full name
                                                                .... family SΣI0..1stringFamily name (often called 'Surname')SΣ1..1stringFamily name (often called 'Surname')
                                                                • Elements differ in comments: 'Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).' vs 'Where an individual has only one name, payers SHALL provide the information as family name to ensure consistency.'
                                                                • Element minimum cardinalities differ: '0' vs '1'
                                                                .... given SΣI0..*stringGiven names (not always 'first'). Includes middle names
                                                                This repeating element order: Given Names appear in the correct order for presenting the name
                                                                SΣ0..*stringGiven names (not always 'first'). Includes middle names
                                                                This repeating element order: Given Names appear in the correct order for presenting the name
                                                                  .... prefix Σ0..*stringParts that come before the name
                                                                  This repeating element order: Prefixes appear in the correct order for presenting the name
                                                                  Σ0..*stringParts that come before the name
                                                                  This repeating element order: Prefixes appear in the correct order for presenting the name
                                                                    .... suffix Σ0..*stringParts that come after the name
                                                                    This repeating element order: Suffixes appear in the correct order for presenting the name
                                                                    Σ0..*stringParts that come after the name
                                                                    This repeating element order: Suffixes appear in the correct order for presenting the name
                                                                      .... period Σ0..1PeriodTime period when name was/is in useΣ0..1PeriodTime period when name was/is in use
                                                                        ... telecom Σ0..*ContactPointA contact detail for the individual
                                                                        Σ0..*ContactPointA contact detail for the individual
                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                            .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                            Slice: Unordered, Open by value:url
                                                                            0..*ExtensionAdditional content defined by implementations
                                                                            Slice: Unordered, Open by value:url
                                                                              .... system SΣI1..1codephone | fax | email | pager | url | sms | other
                                                                              Binding: ContactPointSystem (required): Telecommunications form for contact point.

                                                                              ΣI0..1codephone | fax | email | pager | url | sms | other
                                                                              Binding: ContactPointSystem (required): Telecommunications form for contact point.

                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              • Element minimum cardinalities differ: '1' vs '0'
                                                                              .... value SΣ1..1stringThe actual contact point detailsΣ0..1stringThe actual contact point details
                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              • Element minimum cardinalities differ: '1' vs '0'
                                                                              .... use ?!SΣ0..1codehome | work | temp | old | mobile - purpose of this contact point
                                                                              Binding: ContactPointUse (required)
                                                                              ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
                                                                              Binding: ContactPointUse (required): Use of contact point.

                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                              .... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)Σ0..1positiveIntSpecify preferred order of use (1 = highest)
                                                                                .... period Σ0..1PeriodTime period when the contact point was/is in useΣ0..1PeriodTime period when the contact point was/is in use
                                                                                  ... gender SΣ1..1codemale | female | other | unknown
                                                                                  Binding: AdministrativeGender (required)
                                                                                  Σ0..1codemale | female | other | unknown
                                                                                  Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

                                                                                  • Elements differ in comments: 'The gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a "hard" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.' vs 'MAY be excluded. Gender is not a data element typically found on physical insurance cards. Furthermore, self-identified gender may change over time. Including this element could create a situation where the gender element in the provided resource does not match that in another form of identification or does not match the member's self-identified gender.'
                                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                                                  ... birthDate SΣ0..1dateThe date of birth for the individualΣ0..1dateThe date of birth for the individual
                                                                                  • Elements differ in comments: 'At least an estimated year should be provided as a guess if the real DOB is unknown There is a standard extension "patient-birthTime" available that should be used where Time is required (such as in maternity/infant care systems).' vs 'MAY be excluded. This data element is printed on some physical insurance cards, but not all.'
                                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                  ... deceased[x] ?!Σ0..1boolean, dateTimeIndicates if the individual is deceased or not?!Σ0..1boolean, dateTimeIndicates if the individual is deceased or not
                                                                                    ... address SΣ0..*AddressAn address for the individual
                                                                                    Σ0..*AddressAn address for the individual
                                                                                    • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                      Slice: Unordered, Open by value:url
                                                                                      0..*ExtensionAdditional content defined by implementations
                                                                                      Slice: Unordered, Open by value:url
                                                                                        .... use ?!Σ0..1codehome | work | temp | old | billing - purpose of this address
                                                                                        Binding: AddressUse (required): The use of an address.


                                                                                        Example General: home
                                                                                        ?!Σ0..1codehome | work | temp | old | billing - purpose of this address
                                                                                        Binding: AddressUse (required): The use of an address.


                                                                                        Example General: home
                                                                                          .... type Σ0..1codepostal | physical | both
                                                                                          Binding: AddressType (required): The type of an address (physical / postal).


                                                                                          Example General: both
                                                                                          Σ0..1codepostal | physical | both
                                                                                          Binding: AddressType (required): The type of an address (physical / postal).


                                                                                          Example General: both
                                                                                            .... text Σ0..1stringText representation of the address
                                                                                            Example General: 137 Nowhere Street, Erewhon 9132
                                                                                            Σ0..1stringText representation of the address
                                                                                            Example General: 137 Nowhere Street, Erewhon 9132
                                                                                              .... line SΣ0..*stringStreet name, number, direction & P.O. Box etc.
                                                                                              This repeating element order: The order in which lines should appear in an address label
                                                                                              Example General: 137 Nowhere Street
                                                                                              Σ0..*stringStreet name, number, direction & P.O. Box etc.
                                                                                              This repeating element order: The order in which lines should appear in an address label
                                                                                              Example General: 137 Nowhere Street
                                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                              .... city SΣ0..1stringName of city, town etc.
                                                                                              Example General: Erewhon
                                                                                              Σ0..1stringName of city, town etc.
                                                                                              Example General: Erewhon
                                                                                              • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                              .... district Σ0..1stringDistrict name (aka county)
                                                                                              Example General: Madison
                                                                                              Σ0..1stringDistrict name (aka county)
                                                                                              Example General: Madison
                                                                                                .... state SΣ0..1stringSub-unit of country (abbreviations ok)
                                                                                                Binding: USPS Two Letter Alphabetic Codes (extensible): Two Letter USPS alphabetic codes.

                                                                                                Σ0..1stringSub-unit of country (abbreviations ok)
                                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                .... postalCode SΣ0..1stringUS Zip Codes
                                                                                                Example General: 9132
                                                                                                Σ0..1stringPostal code for area
                                                                                                Example General: 9132
                                                                                                • Elements differ in short: 'US Zip Codes' vs 'Postal code for area'
                                                                                                • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                .... country Σ0..1stringCountry (e.g. can be ISO 3166 2 or 3 letter code)Σ0..1stringCountry (e.g. can be ISO 3166 2 or 3 letter code)
                                                                                                  .... period SΣ0..1PeriodTime period when address was/is in use
                                                                                                  Example General: {"start":"2010-03-23","end":"2010-07-01"}
                                                                                                  Σ0..1PeriodTime period when address was/is in use
                                                                                                  Example General: {"start":"2010-03-23","end":"2010-07-01"}
                                                                                                  • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                  ... maritalStatus 0..1CodeableConceptMarital (civil) status of a patient
                                                                                                  Binding: Marital Status Codes (extensible): The domestic partnership status of a person.

                                                                                                  0..1CodeableConceptMarital (civil) status of a patient
                                                                                                  Binding: Marital Status Codes (extensible): The domestic partnership status of a person.

                                                                                                    ... multipleBirth[x] 0..1boolean, integerWhether patient is part of a multiple birth0..1boolean, integerWhether patient is part of a multiple birth
                                                                                                      ... photo 0..*AttachmentImage of the patient
                                                                                                      0..*AttachmentImage of the patient
                                                                                                        ... contact I0..*BackboneElementA contact party (e.g. guardian, partner, friend) for the patient
                                                                                                        I0..*BackboneElementA contact party (e.g. guardian, partner, friend) for the patient
                                                                                                          .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                            .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                            0..*ExtensionAdditional content defined by implementations
                                                                                                              .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                              ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                .... relationship 0..*CodeableConceptThe kind of relationship
                                                                                                                Binding: PatientContactRelationship (extensible): The nature of the relationship between a patient and a contact person for that patient.


                                                                                                                0..*CodeableConceptThe kind of relationship
                                                                                                                Binding: PatientContactRelationship (extensible): The nature of the relationship between a patient and a contact person for that patient.


                                                                                                                  .... name 0..1HumanNameA name associated with the contact person0..1HumanNameA name associated with the contact person
                                                                                                                    .... telecom 0..*ContactPointA contact detail for the person
                                                                                                                    0..*ContactPointA contact detail for the person
                                                                                                                      .... address 0..1AddressAddress for the contact person0..1AddressAddress for the contact person
                                                                                                                        .... gender 0..1codemale | female | other | unknown
                                                                                                                        Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

                                                                                                                        0..1codemale | female | other | unknown
                                                                                                                        Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

                                                                                                                          .... organization I0..1Reference(Organization)Organization that is associated with the contactI0..1Reference(Organization)Organization 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 patient0..1PeriodThe period during which this contact person or organization is valid to be contacted relating to this patient
                                                                                                                              ... communication 0..*BackboneElementA language which may be used to communicate with the patient about his or her health
                                                                                                                              0..*BackboneElementA language which may be used to communicate with the patient about his or her health
                                                                                                                                .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                  .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                  0..*ExtensionAdditional content defined by implementations
                                                                                                                                    .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                    ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                      .... language S1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
                                                                                                                                      Binding: Language codes with language and optionally a region modifier (extensible)
                                                                                                                                      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
                                                                                                                                      • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                                                                                                      .... preferred 0..1booleanLanguage preference indicator0..1booleanLanguage preference indicator
                                                                                                                                        ... generalPractitioner 0..*Reference(Organization | Practitioner | PractitionerRole)Patient's nominated primary care provider
                                                                                                                                        0..*Reference(Organization | Practitioner | PractitionerRole)Patient's nominated primary care provider
                                                                                                                                          ... managingOrganization Σ0..1Reference(Organization)Organization that is the custodian of the patient recordΣ0..1Reference(Organization)Organization that is the custodian of the patient record
                                                                                                                                            ... link ?!Σ0..*BackboneElementLink to another patient resource that concerns the same actual person
                                                                                                                                            ?!Σ0..*BackboneElementLink to another patient resource that concerns the same actual person
                                                                                                                                              .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                                                .... extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                                                0..*ExtensionAdditional content defined by implementations
                                                                                                                                                  .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                  ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                                                                                                                                    .... other Σ1..1Reference(Patient | RelatedPerson)The other patient or related person resource that the link refers toΣ1..1Reference(Patient | RelatedPerson)The other patient or related person resource that the link refers to
                                                                                                                                                      .... type Σ1..1codereplaced-by | replaces | refer | seealso
                                                                                                                                                      Binding: LinkType (required): The type of link between this patient resource and another patient resource.

                                                                                                                                                      Σ1..1codereplaced-by | replaces | refer | seealso
                                                                                                                                                      Binding: LinkType (required): The type of link between this patient resource and another patient resource.


                                                                                                                                                        doco Documentation for this format