Profile Comparison between http://fhir.org/guides/argonaut/StructureDefinition/argo-patient vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient

Left:Argonaut Patient Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-patient)
Right:US Core Patient Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-patient' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient'
InformationStructureDefinition.nameValues for name differ: 'Argonaut Patient Profile' vs 'USCorePatientProfile'
InformationStructureDefinition.statusValues for status differ: 'draft' vs 'active'
InformationStructureDefinition.dateValues for date differ: '2016-10-18T00:00:00+11:00' vs '2022-09-30'
InformationStructureDefinition.publisherValues for publisher differ: 'Argonaut Project' vs 'HL7 International - Cross-Group Projects'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#US'
WarningStructureDefinition.fhirVersionValues for fhirVersion differ: '1.0.2' vs '4.0.1'
WarningPatientElements differ in short: 'Argonaut Patient Profile' vs 'Information about an individual or animal receiving health care services'
WarningPatientElements differ in definition: 'Demographics and other administrative information about an individual or animal receiving care or other health-related services.' vs '\-'
InformationPatientStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.contained.empty())
InformationPatientStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
InformationPatientStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
InformationPatientStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
InformationPatientStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (text.`div`.exists())
WarningPatient.idElements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
WarningPatient.metaElements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.'
WarningPatient.implicitRulesElements differ in definition: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
WarningPatient.implicitRulesElements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
WarningPatient.languageElements differ in comments: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
WarningPatient.textElements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
WarningPatient.textElements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'
WarningPatient.containedElements differ in comments: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
WarningPatient.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningPatient.identifierElements differ in short: 'An identifier for this patient' vs '(USCDI) An identifier for this patient'
WarningPatient.identifier.idElements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
WarningPatient.identifier.idElements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
WarningPatient.identifier.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.identifier.useElements differ in short: 'usual | official | temp | secondary (If known)' vs 'usual | official | temp | secondary | old (If known)'
WarningPatient.identifier.useElements differ in comments: 'This is labeled as 'Is Modifier' because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.' vs 'Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.'
WarningPatient.identifier.systemElements differ in short: 'The namespace for the identifier' vs '(USCDI) The namespace for the identifier value'
WarningPatient.identifier.systemElements differ in definition: 'Establishes the namespace in which set of possible id values is unique.' vs 'Establishes the namespace for the value - that is, a URL that describes a set values that are unique.'
WarningPatient.identifier.systemElements differ in requirements: 'There are many sequences of identifiers. To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.' vs 'There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.'
WarningPatient.identifier.valueElements differ in short: 'The value that is unique within the system.' vs '(USCDI) The value that is unique within the system.'
WarningPatient.identifier.valueElements differ in definition: 'The portion of the identifier typically displayed to the user and which is unique within the context of the system.' vs 'The portion of the identifier typically relevant to the user and which is unique within the context of the system.'
WarningPatient.identifier.valueElements differ in comments: 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.' vs 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension]. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.'
WarningPatient.identifier.assignerElements differ in comments: 'The reference may be just a text description of the assigner.' vs 'The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.'
WarningPatient.activeElements differ in definition: 'Whether this patient record is in active use.' vs 'Whether this patient record is in active use. Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules. It is often used to filter patient lists to exclude inactive patients Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death.'
WarningPatient.activeElements differ in comments: 'Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.' vs 'If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.'
WarningPatient.nameElements differ in short: 'A name associated with the patient' vs '(USCDI) A name associated with the patient'
InformationPatient.nameStructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible ((family.exists() or given.exists()) xor extension.where(url='http://hl7.org/fhir/StructureDefinition/data-absent-reason').exists())
WarningPatient.name.idElements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
WarningPatient.name.idElements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
WarningPatient.name.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.name.useElements differ in short: 'usual | official | temp | nickname | anonymous | old | maiden' vs '(USCDI) usual | official | temp | nickname | anonymous | old | maiden'
WarningPatient.name.useElements differ in comments: 'This is labeled as 'Is Modifier' because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old.' vs 'Applications can assume that a name is current unless it explicitly says that it is temporary or old.'
WarningPatient.name.useElements differ in description: 'The use of a human name' vs 'The use of a human name.'
WarningPatient.name.useElements differ in description: 'The use of a human name' vs 'The use of a human name.'
WarningPatient.name.textElements differ in definition: 'A full text representation of the name.' vs 'Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.'
WarningPatient.name.textElements differ in comments: 'Can provide both a text representation and structured parts.' vs 'Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.'
WarningPatient.name.familyElements differ in short: 'Family name (often called 'Surname')' vs '(USCDI) Family name (often called 'Surname')'
WarningPatient.name.familyElements differ in comments: 'For family name, hyphenated names such as 'Smith-Jones' are a single name, but names with spaces such as 'Smith Jones' are broken into multiple parts.' vs 'Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).'
InformationPatient.name.familyElement minimum cardinalities differ: '1' vs '0'
InformationPatient.name.familyElement maximum cardinalities differ: '2147483647' vs '1'
WarningPatient.name.givenElements differ in short: 'Given names (not always 'first'). Includes middle names' vs '(USCDI) Given names (not always 'first'). Includes middle names'
WarningPatient.name.givenElements differ in comments: 'If only initials are recorded, they may be used in place of the full name. Not called 'first name' since given names do not always come first.' vs 'If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called 'first name' since given names do not always come first.'
InformationPatient.name.givenElement minimum cardinalities differ: '1' vs '0'
WarningPatient.name.suffixElements differ in short: 'Parts that come after the name' vs '(USCDI) Parts that come after the name'
WarningPatient.name.periodElements differ in short: 'Time period when name was/is in use' vs '(USCDI) Time period when name was/is in use'
WarningPatient.telecomElements differ in short: 'A contact detail for the individual' vs '(USCDI) A contact detail for the individual'
WarningPatient.telecomElements differ in comments: 'A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address may not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).' vs 'A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).'
WarningPatient.telecom.systemElements differ in short: 'phone | fax | email | pager | url | sms | other' vs '(USCDI) phone | fax | email | pager | url | sms | other'
WarningPatient.telecom.systemElements differ in definition for mustSupport: 'false' vs 'true'
InformationPatient.telecom.systemElement minimum cardinalities differ: '0' vs '1'
WarningPatient.telecom.valueElements differ in short: 'The actual contact point details' vs '(USCDI) The actual contact point details'
WarningPatient.telecom.valueElements differ in definition for mustSupport: 'false' vs 'true'
InformationPatient.telecom.valueElement minimum cardinalities differ: '0' vs '1'
WarningPatient.telecom.useElements differ in short: 'home | work | temp | old | mobile - purpose of this contact point' vs '(USCDI) home | work | temp | old | mobile - purpose of this contact point'
WarningPatient.telecom.useElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.genderElements differ in short: 'male | female | other | unknown' vs '(USCDI) male | female | other | unknown'
WarningPatient.genderElements differ in comments: 'The gender may 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 M and F, though the vast majority of systems and contexts only support M and F. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, 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, chromosonal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a 'hard' error.' vs '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.'
WarningPatient.genderElements differ in requirements: 'Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes.' vs 'Needed for identification of the individual, in combination with (at least) name and birth date.'
WarningPatient.birthDateElements differ in short: 'The date of birth for the individual' vs '(USCDI) The date of birth for the individual'
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 maternaty/infant care systems).' vs '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).'
WarningPatient.deceased[x]Elements differ in short: 'Indicates if the individual is deceased or not' vs '(USCDI) Indicates if the individual is deceased or not'
WarningPatient.deceased[x]Elements differ in comments: 'If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.' vs 'If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.'
WarningPatient.addressElements differ in short: 'Addresses for the individual' vs '(USCDI) An address for the individual'
WarningPatient.addressElements differ in definition: 'Addresses for the individual.' vs 'An address for the individual.'
WarningPatient.addressElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.address.useElements differ in short: 'home | work | temp | old | billing - purpose of this address' vs '(USCDI) home | work | temp | old | billing - purpose of this address'
WarningPatient.address.lineElements differ in short: 'Street name, number, direction & P.O. Box etc.' vs '(USCDI) Street name, number, direction & P.O. Box etc.'
WarningPatient.address.lineElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.address.cityElements differ in short: 'Name of city, town etc.' vs '(USCDI) Name of city, town etc.'
WarningPatient.address.cityElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.address.stateElements differ in short: 'Sub-unit of country (abbreviations ok)' vs '(USCDI) Sub-unit of country (abbreviations ok)'
WarningPatient.address.stateElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.address.postalCodeElements differ in short: 'Postal code for area' vs '(USCDI) US Zip Codes'
WarningPatient.address.postalCodeElements differ in definition for mustSupport: 'false' vs 'true'
WarningPatient.address.periodElements differ in short: 'Time period when address was/is in use' vs '(USCDI) Time period when address was/is in use'
WarningPatient.multipleBirth[x]Elements differ in definition: 'Indicates whether the patient is part of a multiple or indicates the actual birth order.' vs 'Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).'
WarningPatient.contact.idElements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
WarningPatient.contact.idElements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
WarningPatient.contact.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.contact.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
WarningPatient.contact.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
ErrorPatient.contact.relationshipUnable to resolve left value set http://hl7.org/fhir/ValueSet/patient-contact-relationship at Patient.contact.relationship
WarningPatient.communicationElements differ in short: 'A list of Languages which may be used to communicate with the patient about his or her health' vs '(USCDI) A language which may be used to communicate with the patient about his or her health'
WarningPatient.communicationElements differ in definition: 'Languages which may be used to communicate with the patient about his or her health.' vs 'A language which may be used to communicate with the patient about his or her health.'
WarningPatient.communicationElements differ in comments: 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.' vs 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.'
WarningPatient.communicationElements differ in requirements: 'If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.' vs 'If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.'
WarningPatient.communicationElements differ in definition for mustSupport: 'true' vs 'false'
WarningPatient.communication.idElements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
WarningPatient.communication.idElements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
WarningPatient.communication.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.communication.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
WarningPatient.communication.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningPatient.communication.languageElements differ in short: 'The language which can be used to communicate with the patient about his or her health' vs '(USCDI) The language which can be used to communicate with the patient about his or her health'
WarningPatient.linkElements differ in requirements: 'There are multiple usecases: * Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers.' vs 'There are multiple use cases: * Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers.'
WarningPatient.link.idElements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
WarningPatient.link.idElements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
WarningPatient.link.extensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.link.modifierExtensionElements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
WarningPatient.link.modifierExtensionElements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
WarningPatient.link.otherElements differ in short: 'The other patient resource that the link refers to' vs 'The other patient or related person resource that the link refers to'
WarningPatient.link.typeElements differ in short: 'replace | refer | seealso - type of link' vs 'replaced-by | replaces | refer | seealso'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Patient
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Added the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2016-10-18T00:00:00+11:002022-09-30
      • Values Differ
      .descriptionThe US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v3 '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 and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
      • Added the item 'The US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v3 '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 and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.'
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion1.0.24.0.1
      • Values Differ
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
        • Added the item 'urn:iso:std:iso:3166#US'
        .kindresource
          .nameArgonaut Patient ProfileUSCorePatientProfile
          • Values Differ
          .publisherArgonaut ProjectHL7 International - Cross-Group Projects
          • Values Differ
          .purpose
            .statusdraftactive
            • Values Differ
            .titleUS Core Patient Profile
            • Added the item 'US Core Patient Profile'
            .typePatient
              .urlhttp://fhir.org/guides/argonaut/StructureDefinition/argo-patienthttp://hl7.org/fhir/us/core/StructureDefinition/us-core-patient
              • Values Differ
              .version6.0.0
              • Added the item '6.0.0'

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
              .. Patient 0..*PatientArgonaut Patient Profile
              0..*PatientInformation about an individual or animal receiving health care services
              • Elements differ in short: 'Argonaut Patient Profile' vs 'Information about an individual or animal receiving health care services'
              • Elements differ in definition: 'Demographics and other administrative information about an individual or animal receiving care or other health-related services.' vs '\-'
              • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.contained.empty())
              • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
              • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
              • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
              • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (text.`div`.exists())
              ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
              • Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
              ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
              • Elements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.'
              ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
              • Elements differ in definition: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
              • Elements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
              ... language 0..1codeLanguage of the resource content
              Binding: todo (required): A human language.

              0..1codeLanguage of the resource content
              Binding: todo (preferred): A human language.

              Additional BindingsPurpose
              todoMax Binding
              • Elements differ in comments: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
              ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
              • Elements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
              • Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.'
              ... contained 0..*ResourceContained, inline Resources
              0..*ResourceContained, inline Resources
              • Elements differ in comments: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
              ... Slices for extension 0..*ExtensionExtension
              Slice: Unordered, Open by value:url
              0..*ExtensionExtension
              Slice: Unordered, Open by value:url
                ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                ?!0..*ExtensionExtensions that cannot be ignored
                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                ... identifier S1..*IdentifierAn identifier for this patient
                SΣ1..*Identifier(USCDI) An identifier for this patient
                • Elements differ in short: 'An identifier for this patient' vs '(USCDI) An identifier for this patient'
                .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                • Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
                • Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
                .... extension 0..*ExtensionAdditional Content defined by implementations
                0..*ExtensionAdditional content defined by implementations
                Slice: Unordered, Open by value:url
                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.'
                .... use ?!Σ0..1codeusual | official | temp | secondary (If known)
                Binding: todo (required): Identifies the purpose for this identifier, if known .

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

                • Elements differ in short: 'usual | official | temp | secondary (If known)' vs 'usual | official | temp | secondary | old (If known)'
                • Elements differ in comments: 'This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.' vs 'Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.'
                .... type Σ0..1CodeableConceptDescription of identifier
                Binding: todo (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: todo (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.

                  .... system S1..1uriThe namespace for the identifier
                  Example General: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
                  SΣ1..1uri(USCDI) The namespace for the identifier value
                  Example General: http://www.acme.com/identifiers/patient
                  • Elements differ in short: 'The namespace for the identifier' vs '(USCDI) The namespace for the identifier value'
                  • Elements differ in definition: 'Establishes the namespace in which set of possible id values is unique.' vs 'Establishes the namespace for the value - that is, a URL that describes a set values that are unique.'
                  • Elements differ in requirements: 'There are many sequences of identifiers. To perform matching, we need to know what sequence we're dealing with. The system identifies a particular sequence or set of unique identifiers.' vs 'There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.'
                  .... value S1..1stringThe value that is unique within the system.
                  Example General: 123456
                  SΣ1..1string(USCDI) The value that is unique within the system.
                  Example General: 123456
                  • Elements differ in short: 'The value that is unique within the system.' vs '(USCDI) The value that is unique within the system.'
                  • Elements differ in definition: 'The portion of the identifier typically displayed to the user and which is unique within the context of the system.' vs 'The portion of the identifier typically relevant to the user and which is unique within the context of the system.'
                  • Elements differ in comments: 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.' vs 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension]. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.'
                  .... 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)
                    • Elements differ in comments: 'The reference may be just a text description of the assigner.' vs 'The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.'
                    ... active ?!Σ0..1booleanWhether this patient's record is in active use?!Σ0..1booleanWhether this patient's record is in active use
                    • Elements differ in definition: 'Whether this patient record is in active use.' vs 'Whether this patient record is in active use. Many systems use this property to mark as non-current patients, such as those that have not been seen for a period of time based on an organization's business rules. It is often used to filter patient lists to exclude inactive patients Deceased patients may also be marked as inactive for the same reasons, but may be active for some time after death.'
                    • Elements differ in comments: 'Default is true. If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.' vs 'If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient.'
                    ... name S1..*HumanNameA name associated with the patient
                    SΣC1..*HumanName(USCDI) A name associated with the patient
                    us-core-6: At least name.given and/or name.family are present or, if neither is available, the Data Absent Reason Extension is present.
                    • Elements differ in short: 'A name associated with the patient' vs '(USCDI) A name associated with the patient'
                    • StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible ((family.exists() or given.exists()) xor extension.where(url='http://hl7.org/fhir/StructureDefinition/data-absent-reason').exists())
                    .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                    • Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
                    • Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
                    .... extension 0..*ExtensionAdditional Content defined by implementations
                    0..*ExtensionAdditional content defined by implementations
                    Slice: Unordered, Open by value:url
                    • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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.'
                    .... use ?!Σ0..1codeusual | official | temp | nickname | anonymous | old | maiden
                    Binding: todo (required): The use of a human name

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

                    • Elements differ in short: 'usual | official | temp | nickname | anonymous | old | maiden' vs '(USCDI) usual | official | temp | nickname | anonymous | old | maiden'
                    • Elements differ in comments: 'This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old.' vs 'Applications can assume that a name is current unless it explicitly says that it is temporary or old.'
                    • Elements differ in description: 'The use of a human name' vs 'The use of a human name.'
                    • Elements differ in description: 'The use of a human name' vs 'The use of a human name.'
                    .... text Σ0..1stringText representation of the full nameΣ0..1stringText representation of the full name
                    • Elements differ in definition: 'A full text representation of the name.' vs 'Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.'
                    • Elements differ in comments: 'Can provide both a text representation and structured parts.' vs 'Can provide both a text representation and parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.'
                    .... family S1..*stringFamily name (often called 'Surname')
                    SΣC0..1string(USCDI) Family name (often called 'Surname')
                    • Elements differ in short: 'Family name (often called 'Surname')' vs '(USCDI) Family name (often called 'Surname')'
                    • Elements differ in comments: 'For family name, hyphenated names such as "Smith-Jones" are a single name, but names with spaces such as "Smith Jones" are broken into multiple parts.' vs 'Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).'
                    • Element minimum cardinalities differ: '1' vs '0'
                    • Element maximum cardinalities differ: '2147483647' vs '1'
                    .... given S1..*stringGiven names (not always 'first'). Includes middle names
                    SΣC0..*string(USCDI) Given names (not always 'first'). Includes middle names
                    This repeating element order: Given Names appear in the correct order for presenting the name
                    • Elements differ in short: 'Given names (not always 'first'). Includes middle names' vs '(USCDI) Given names (not always 'first'). Includes middle names'
                    • Elements differ in comments: 'If only initials are recorded, they may be used in place of the full name. Not called "first name" since given names do not always come first.' vs 'If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations. This element is not called "first name" since given names do not always come first.'
                    • Element minimum cardinalities differ: '1' vs '0'
                    .... prefix Σ0..*stringParts that come before 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
                      Σ0..*string(USCDI) Parts that come after the name
                      This repeating element order: Suffixes appear in the correct order for presenting the name
                      • Elements differ in short: 'Parts that come after the name' vs '(USCDI) Parts that come after the name'
                      .... period Σ0..1PeriodTime period when name was/is in useΣ0..1Period(USCDI) Time period when name was/is in use
                      • Elements differ in short: 'Time period when name was/is in use' vs '(USCDI) Time period when name was/is in use'
                      ... telecom Σ0..*ContactPointA contact detail for the individual
                      Σ0..*ContactPoint(USCDI) A contact detail for the individual
                      • Elements differ in short: 'A contact detail for the individual' vs '(USCDI) A contact detail for the individual'
                      • Elements differ in comments: 'A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address may not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).' vs 'A Patient may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification. The address might not go directly to the individual, but may reach another party that is able to proxy for the patient (i.e. home phone, or pet owner's phone).'
                      .... 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 ΣC0..1codephone | fax | email | pager | url | sms | other
                          Binding: todo (required): Telecommunications form for contact point.

                          SΣC1..1code(USCDI) phone | fax | email | pager | url | sms | other
                          Binding: todo (required): Telecommunications form for contact point.

                          • Elements differ in short: 'phone | fax | email | pager | url | sms | other' vs '(USCDI) phone | fax | email | pager | url | sms | other'
                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                          • Element minimum cardinalities differ: '0' vs '1'
                          .... value Σ0..1stringThe actual contact point detailsSΣ1..1string(USCDI) The actual contact point details
                          • Elements differ in short: 'The actual contact point details' vs '(USCDI) The actual contact point details'
                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                          • Element minimum cardinalities differ: '0' vs '1'
                          .... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
                          Binding: todo (required): Use of contact point.

                          ?!SΣ0..1code(USCDI) home | work | temp | old | mobile - purpose of this contact point
                          Binding: todo (required)
                          • Elements differ in short: 'home | work | temp | old | mobile - purpose of this contact point' vs '(USCDI) home | work | temp | old | mobile - purpose of this contact point'
                          • Elements differ in definition for mustSupport: 'false' vs 'true'
                          .... 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 S1..1codemale | female | other | unknown
                              Binding: todo (required)
                              SΣ1..1code(USCDI) male | female | other | unknown
                              Binding: todo (required)
                              • Elements differ in short: 'male | female | other | unknown' vs '(USCDI) male | female | other | unknown'
                              • Elements differ in comments: 'The gender may 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 M and F, though the vast majority of systems and contexts only support M and F. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific gender aspect of interest (anatomical, chromosonal, 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, chromosonal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overrideable error, not a "hard" error.' vs '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.'
                              • Elements differ in requirements: 'Needed for identification of the individual, in combination with (at least) name and birth date. Gender of individual drives many clinical processes.' vs 'Needed for identification of the individual, in combination with (at least) name and birth date.'
                              ... birthDate S0..1dateThe date of birth for the individualSΣ0..1date(USCDI) The date of birth for the individual
                              • Elements differ in short: 'The date of birth for the individual' vs '(USCDI) The 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 maternaty/infant care systems).' vs '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).'
                              ... deceased[x] ?!Σ0..1boolean, dateTimeIndicates if the individual is deceased or not?!Σ0..1boolean, dateTime(USCDI) Indicates if the individual is deceased or not
                              • Elements differ in short: 'Indicates if the individual is deceased or not' vs '(USCDI) Indicates if the individual is deceased or not'
                              • Elements differ in comments: 'If there's no value in the instance it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.' vs 'If there's no value in the instance, it means there is no statement on whether or not the individual is deceased. Most systems will interpret the absence of a value as a sign of the person being alive.'
                              ... address Σ0..*AddressAddresses for the individual
                              SΣ0..*Address(USCDI) An address for the individual
                              • Elements differ in short: 'Addresses for the individual' vs '(USCDI) An address for the individual'
                              • Elements differ in definition: 'Addresses for the individual.' vs 'An address for the individual.'
                              • Elements differ in definition for mustSupport: 'false' vs 'true'
                              .... 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: todo (required): The use of an address.


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


                                  Example General: home
                                  • Elements differ in short: 'home | work | temp | old | billing - purpose of this address' vs '(USCDI) home | work | temp | old | billing - purpose of this address'
                                  .... type Σ0..1codepostal | physical | both
                                  Binding: todo (required): The type of an address (physical / postal).


                                  Example General: both
                                  Σ0..1codepostal | physical | both
                                  Binding: todo (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 Σ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
                                      SΣ0..*string(USCDI) Street 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 short: 'Street name, number, direction & P.O. Box etc.' vs '(USCDI) Street name, number, direction & P.O. Box etc.'
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      .... city Σ0..1stringName of city, town etc.
                                      Example General: Erewhon
                                      SΣ0..1string(USCDI) Name of city, town etc.
                                      Example General: Erewhon
                                      • Elements differ in short: 'Name of city, town etc.' vs '(USCDI) Name of city, town etc.'
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      .... district Σ0..1stringDistrict name (aka county)
                                      Example General: Madison
                                      Σ0..1stringDistrict name (aka county)
                                      Example General: Madison
                                        .... state Σ0..1stringSub-unit of country (abbreviations ok)SΣ0..1string(USCDI) Sub-unit of country (abbreviations ok)
                                        Binding: todo (extensible): Two Letter USPS alphabetic codes.

                                        • Elements differ in short: 'Sub-unit of country (abbreviations ok)' vs '(USCDI) Sub-unit of country (abbreviations ok)'
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        .... postalCode Σ0..1stringPostal code for area
                                        Example General: 9132
                                        SΣ0..1string(USCDI) US Zip Codes
                                        Example General: 9132
                                        • Elements differ in short: 'Postal code for area' vs '(USCDI) US Zip Codes'
                                        • Elements differ in definition for mustSupport: 'false' vs 'true'
                                        .... 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 Σ0..1PeriodTime period when address was/is in use
                                          Example General: {"start":"2010-03-23","end":"2010-07-01"}
                                          Σ0..1Period(USCDI) Time period when address was/is in use
                                          Example General: {"start":"2010-03-23","end":"2010-07-01"}
                                          • Elements differ in short: 'Time period when address was/is in use' vs '(USCDI) Time period when address was/is in use'
                                          ... maritalStatus 0..1CodeableConceptMarital (civil) status of a patient
                                          Binding: todo (required): The domestic partnership status of a person.

                                          0..1CodeableConceptMarital (civil) status of a patient
                                          Binding: todo (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
                                            • Elements differ in definition: 'Indicates whether the patient is part of a multiple or indicates the actual birth order.' vs 'Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer).'
                                            ... photo 0..*AttachmentImage of the patient
                                            0..*AttachmentImage of the patient
                                              ... contact C0..*BackboneElementA 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
                                              C0..*BackboneElementA contact party (e.g. guardian, partner, friend) for the patient
                                                .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                                                • Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
                                                • Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
                                                .... extension 0..*ExtensionAdditional Content defined by implementations
                                                0..*ExtensionAdditional content defined by implementations
                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 even if unrecognized
                                                • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                                .... relationship 0..*CodeableConceptThe kind of relationship
                                                Binding: todo (extensible): The nature of the relationship between a patient and a contact person for that patient.


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


                                                • Unable to resolve left value set http://hl7.org/fhir/ValueSet/patient-contact-relationship at Patient.contact.relationship
                                                .... 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: todo (required): The gender of a person used for administrative purposes.

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

                                                        .... organization C0..1Reference(Organization)Organization that is associated with the contactC0..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
                                                            ... animal ?!0..0
                                                            • Removed this element
                                                            ... communication S0..*BackboneElementA list of Languages which may be used to communicate with the patient about his or her health
                                                            0..*BackboneElement(USCDI) A language which may be used to communicate with the patient about his or her health
                                                            • Elements differ in short: 'A list of Languages which may be used to communicate with the patient about his or her health' vs '(USCDI) A language which may be used to communicate with the patient about his or her health'
                                                            • Elements differ in definition: 'Languages which may be used to communicate with the patient about his or her health.' vs 'A language which may be used to communicate with the patient about his or her health.'
                                                            • Elements differ in comments: 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.' vs 'If no language is specified, this *implies* that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple Patient.Communication associations. For animals, language is not a relevant field, and should be absent from the instance. If the Patient does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.'
                                                            • Elements differ in requirements: 'If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest.' vs 'If a patient does not speak the local language, interpreters may be required, so languages spoken and proficiency are important things to keep track of both for patient and other persons of interest.'
                                                            • Elements differ in definition for mustSupport: 'true' vs 'false'
                                                            .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                                                            • Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
                                                            • Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
                                                            .... extension 0..*ExtensionAdditional Content defined by implementations
                                                            0..*ExtensionAdditional content defined by implementations
                                                            • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 even if unrecognized
                                                            • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
                                                            • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                                            .... language S1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
                                                            Binding: todo (required)
                                                            S1..1CodeableConcept(USCDI) The language which can be used to communicate with the patient about his or her health
                                                            Binding: todo (extensible)
                                                            • Elements differ in short: 'The language which can be used to communicate with the patient about his or her health' vs '(USCDI) The language which can be used to communicate with the patient about his or her health'
                                                            .... preferred 0..1booleanLanguage preference indicator0..1booleanLanguage preference indicator
                                                              ... careProvider 0..*Reference(Organization | Practitioner)Patient's nominated primary care provider
                                                              • Removed this element
                                                              ... 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
                                                                • Elements differ in requirements: 'There are multiple usecases: * Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers.' vs 'There are multiple use cases: * Duplicate patient records due to the clerical errors associated with the difficulties of identifying humans consistently, and * Distribution of patient information across multiple servers.'
                                                                .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                                                                • Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
                                                                • Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
                                                                .... extension 0..*ExtensionAdditional Content defined by implementations
                                                                0..*ExtensionAdditional content defined by implementations
                                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 even if unrecognized
                                                                • Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
                                                                • Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
                                                                .... other ?!1..1Reference(Patient)The other patient resource that the link refers toΣ1..1Reference(Patient | RelatedPerson)The other patient or related person resource that the link refers to
                                                                • Elements differ in short: 'The other patient resource that the link refers to' vs 'The other patient or related person resource that the link refers to'
                                                                .... type ?!1..1codereplace | refer | seealso - type of link
                                                                Binding: todo (required): The type of link between this patient resource and another patient resource.

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

                                                                • Elements differ in short: 'replace | refer | seealso - type of link' vs 'replaced-by | replaces | refer | seealso'
                                                                ... generalPractitioner 0..*Reference(Organization | Practitioner | PractitionerRole)Patient's nominated primary care provider
                                                                • Added this element

                                                                doco Documentation for this format