| Error | StructureDefinition.url | Values for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-patient' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient' |
| Information | StructureDefinition.name | Values for name differ: 'Argonaut Patient Profile' vs 'USCorePatientProfile' |
| Information | StructureDefinition.status | Values for status differ: 'draft' vs 'active' |
| Information | StructureDefinition.date | Values for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects' |
| Information | StructureDefinition.jurisdiction | Added the item 'urn:iso:std:iso:3166#US' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '1.0.2' vs '4.0.1' |
| Information | StructureDefinition.short | Values for short differ: 'Argonaut Patient Profile' vs 'Information about an individual or animal receiving health care services' |
| Information | StructureDefinition.definition | Values for definition differ: 'Demographics and other administrative information about an individual or animal receiving care or other health-related services.' vs '\-' |
| Information | Patient | StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (contained.contained.empty()) |
| Information | Patient | 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()) |
| Information | Patient | 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()) |
| Information | Patient | 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()) |
| Information | Patient | StructureDefinition USCorePatientProfile has added constraint that is not found in Argonaut Patient Profile and it is uncertain whether they are compatible (text.`div`.exists()) |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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).' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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).' |
| Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'usual | official | temp | secondary (If known)' vs 'usual | official | temp | secondary | old (If known)' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'The namespace for the identifier' vs 'The namespace for the identifier value' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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](http://hl7.org/fhir/R4/extension-rendered-value.html). 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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | Patient.name | 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()) |
| Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'usual | official | temp | nickname | anonymous | old | maiden' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: usual | official | temp | nickname | anonymous | old | maiden' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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).' |
| Information | Patient.name.family | Element minimum cardinalities differ: '1' vs '0' |
| Information | Patient.name.family | Element maximum cardinalities differ: '2147483647' vs '1' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | Patient.name.given | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'Parts that come after the name' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Parts that come after the name' |
| Information | StructureDefinition.short | Values for short differ: 'Time period when name was/is in use' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Time period when name was/is in use' |
| Information | StructureDefinition.short | Values for short differ: 'A contact detail for the individual' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: A contact detail for the individual' |
| Information | StructureDefinition.comment | Values for comment differ: '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).' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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).' |
| Information | StructureDefinition.short | Values for short differ: 'Indicates if the individual is deceased or not' vs '𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Indicates if the individual is deceased or not' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Addresses for the individual' vs 'An address for the individual' |
| Information | StructureDefinition.definition | Values for definition differ: 'Addresses for the individual.' vs 'An address for the individual.' |
| Warning | Patient.address | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | StructureDefinition.definition | Values for definition differ: '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).' |
| Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
| Information | StructureDefinition.definition | Values for definition differ: '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).' |
| Error | Patient.contact.relationship | Unable to resolve left value set http://hl7.org/fhir/ValueSet/patient-contact-relationship at Patient.contact.relationship |
| Information | StructureDefinition.short | Values for short differ: 'A list of 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' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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.' |
| Warning | Patient.communication | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
| Information | StructureDefinition.definition | Values for definition differ: '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).' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' |
| Information | StructureDefinition.short | Values for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized' |
| Information | StructureDefinition.definition | Values for definition differ: '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).' |
| Information | StructureDefinition.short | Values for short differ: 'The other patient resource that the link refers to' vs 'The other patient or related person resource that the link refers to' |
| Information | StructureDefinition.short | Values for short differ: 'replace | refer | seealso - type of link' vs 'replaced-by | replaces | refer | seealso' |
abstract
jurisdiction[0]
Patient
modifierExtension