Profile Comparison between http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Decedent vs http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Decedent

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient
copyright
date	2019-03-27T07:24:20+11:00	2020-05-09	Values Differ
description
experimental		false	Added the item 'false'
fhirVersion	3.0.1	4.0.1	Values Differ
jurisdiction
jurisdiction[0]		urn:iso:std:iso:3166#US	Added the item 'urn:iso:std:iso:3166#US'
kind	resource
name	VRDR Decedent	Decedent	Values Differ
publisher	Hi3 Solutions	Health Level Seven International	Values Differ
purpose
status	draft	active	Values Differ
title		VRDR Decedent	Added the item 'VRDR Decedent'
type	Patient
url	http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Decedent
version	0.1.0	1.0.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Patient									Elements differ in short: "US Core Patient Profile" "Information about an individual or animal receiving health care services"
id	Σ				Σ				Elements differ in short: "id" "Logical id of this artifact" Elements differ in definition: "MAY contain zero or one [0..1] id (CONF:4393-106)." "The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes."
meta	Σ				Σ				Elements differ in short: "meta" "Metadata about the resource" Elements differ in definition: "MAY contain zero or one [0..1] meta (CONF:4393-107)." "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	?!Σ				?!Σ				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." "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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation." "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									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)." "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									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." "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. 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 in formation is added later." "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									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." "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."
extension			Extension				Extension		Elements differ in definition: "SHOULD contain zero or one [0..1] extension (CONF:4393-92) such that it" "An Extension"
modifierExtension	?!				?!				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." "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	SΣ				SΣ				Elements differ in short: "identifier" "An identifier for this patient" Elements differ in definition: "SHOULD contain zero or one [0..1] identifier (CONF:4393-6)." "An identifier for this patient."
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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	?!Σ				?!Σ				Elements differ in short: "usual | official | temp | secondary (If known)" "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." "Applications can assume that an identifier is permanent unless it explicitly says that it is temporary."
type	Σ				Σ				Elements differ in short: "type" "Description of identifier" Elements differ in definition: "The identifier, if present, SHALL contain exactly one [1..1] type="BR" Social Beneficiary Identifier (CONF:4393-27)." "A coded type for the identifier that can be used to determine which identifier to use for a specific purpose." Elements differ in comments: "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type." "This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type."
system	SΣ				SΣ				Elements differ in short: "system" "The namespace for the identifier value" Elements differ in definition: "The identifier, if present, SHOULD contain zero or one [0..1] system="2.16.840.1.113883.4.1" United States of America Social Security Number (CONF:4393-28)." "Establishes the namespace for the value - that is, a URL that describes a set values that are unique."
value	SΣ				SΣ				Elements differ in short: "value" "The value that is unique within the system." Elements differ in definition: "The identifier, if present, SHALL contain exactly one [1..1] value (CONF:4393-29)." "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. 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]." "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	Σ				Σ
assigner	Σ				Σ
active	?!Σ				?!Σ				Elements differ in definition: "Whether this patient record is in active use." "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 This element is labeled as a modifier because when the patient record is marked as not active it is not expected to be used/referenced without being changed back to active." "If a record is inactive, and linked to an active record, then future patient/record updates should occur on the other patient."
name	SΣ		(Slice Definition)		SΣI				Elements differ in definition: "SHALL contain exactly one [1..1] name (CONF:4393-43) such that it" "A name associated with the individual." StructureDefinition Decedent has added constraint that is not found in VRDR Decedent and it is uncertain whether they are compatible (family.exists() or given.exists())
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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	?!Σ				?!Σ				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." "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" "The use of a human name." Elements differ in description: "The use of a human name" "The use of a human name."
text	Σ				Σ				Elements differ in definition: "A full text representation of the name." "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." "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	SΣ				SΣI
given	SΣ				SΣI				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." "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."
prefix	Σ				Σ
suffix	Σ				Σ
period	Σ				Σ
telecom	Σ				SΣ				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)." "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)." Elements differ in definition for mustSupport: "false" "true"
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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."
system	ΣI				SΣI				Elements differ in definition for mustSupport: "false" "true" Elements differ in description: "Telecommunications form for contact point" "Telecommunications form for contact point." Elements differ in description: "Telecommunications form for contact point" "Telecommunications form for contact point."
value	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
use	?!Σ				?!SΣ				Elements differ in comments: "This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one. Applications can assume that a contact is current unless it explicitly says that it is temporary or old." "Applications can assume that a contact is current unless it explicitly says that it is temporary or old." Elements differ in definition for mustSupport: "false" "true"
rank	Σ				Σ				Elements differ in definition: "Specifies a preferred order in which to use a set of contacts. Contacts are ranked with lower values coming before higher values." "Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values."
period	Σ				Σ
gender	SΣ				SΣ				Elements differ in short: "gender" "male | female | other | unknown" Elements differ in definition: "SHALL contain exactly one [1..1] gender, which SHALL be selected from ValueSet FHIR AdministrativeGender http://hl7.org/fhir/v3/vs/AdministrativeGender DYNAMIC (CONF:4393-7)." "The observed sex (male, female, or unknown) of the decedent at the time of death as determined by the death certifier or authoritative informant." 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." "This item aids in the identification of the decedent. It is also used in research and statistical analysis to determine sex-specific death rates. This element differs from the US Core BirthSex element. Birthsex is not a concept required for completion of a death record for submission to NCHS. It is included in the VRDR FHIR IG by virtue of using the US Core Patient as the base profile for Decedent. The US Core IG defined BirthSex as a code classifying the person's sex assigned at birth and declares the element as "must support". Labeling an element MustSupport means that implementations that produce or consume resources SHALL provide "support" for the element in some meaningful way. For VRDR meaningful support of the US Core BirthSex element would be the inclusion of birth sex as recorded in the decedents birth record, if known. Birthsex is an optional element and need not be completed if it is unknown." 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." "Needed for identification of the individual, in combination with (at least) name and birth date." Unable to resolve right value set https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.1038 at Patient.gender
birthDate	SΣ				SΣ				Elements differ in short: "birthDate" "The date of birth for the individual" Elements differ in definition: "SHOULD contain zero or one [0..1] birthDate (CONF:4393-8)." "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)." "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]	?!Σ				?!Σ				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. This element is labeled as a modifier because once a patient is marked as deceased, the actions that are appropriate to perform on the patient may be significantly different." "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	Σ		(Slice Definition)		SΣ				Elements differ in short: "Addresses for the individual" "An address for the individual" Elements differ in definition: "SHALL contain zero or one [0..1] address (CONF:4393-35) such that it" "An address for the individual." Elements differ in definition for mustSupport: "false" "true"
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
Within-City-Limits-Indicator			Extension			0..*	Coding	Extension URL: http://hl7.org/fhir/us/vrdr/StructureDefinition/Within-City-Limits-Indicator Slice: Unordered, Open by value:url Binding: https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7486 (required) ele-1: All FHIR elements must have a @value or children ext-1: Must have either extensions or value[x], not both	Elements differ in short: "Additional Content defined by implementations" "Extension" 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." "An Extension"
use	?!Σ				?!Σ				Elements differ in short: "home | work | temp | old - purpose of this address" "home | work | temp | old | billing - purpose of this address" Elements differ in comments: "This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one. Applications can assume that an address is current unless it explicitly says that it is temporary or old." "Applications can assume that an address is current unless it explicitly says that it is temporary or old." Elements differ in description: "The use of an address" "The use of an address." Elements differ in description: "The use of an address" "The use of an address."
type	Σ				Σ				Elements differ in description: "The type of an address (physical / postal)" "The type of an address (physical / postal)." Elements differ in description: "The type of an address (physical / postal)" "The type of an address (physical / postal)."
text	Σ				Σ				Elements differ in definition: "A full text representation of the address." "Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts." Elements differ in comments: "Can provide both a text representation and parts." "Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part."
line	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
city	Σ				SΣ				Elements differ in definition: "The name of the city, town, village or other community or delivery center." "The name of the city, town, suburb, village or other community or delivery center." Elements differ in definition for mustSupport: "false" "true"
district	Σ				Σ
state	Σ				SΣ				Elements differ in definition: "Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes)." "Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes)." Elements differ in definition for mustSupport: "false" "true"
postalCode	Σ				SΣ				Elements differ in short: "Postal code for area" "US Zip Codes" Elements differ in definition for mustSupport: "false" "true"
country	Σ				Σ				Elements differ in comments: "ISO 3166 3 letter codes can be used in place of a full country name." "ISO 3166 3 letter codes can be used in place of a human readable country name."
period	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
maritalStatus									Elements differ in short: "maritalStatus" "Marital (civil) status of a patient" Elements differ in definition: "SHALL contain exactly one [1..1] maritalStatus, which SHALL be selected from ValueSet FHIR MaritalStatus http://hl7.org/fhir/vs/marital-status (CONF:4393-16)." "This field contains a patient's most recent marital (civil) status." Unable to resolve right value set https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7380 at Patient.maritalStatus
multipleBirth[x]									Elements differ in definition: "Indicates whether the patient is part of a multiple (bool) or indicates the actual birth order (integer)." "Indicates whether the patient is part of a multiple (boolean) or indicates the actual birth order (integer)." Elements differ in comments: "Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in tripplets would be valueInteger=2 and the third born would have valueInteger=3 If a bool value was provided for this tripplets examle, then all 3 patient records would have valueBool=true (the ordering is not indicated)." "Where the valueInteger is provided, the number is the birth number in the sequence. E.g. The middle birth in triplets would be valueInteger=2 and the third born would have valueInteger=3 If a boolean value was provided for this triplets example, then all 3 patient records would have valueBoolean=true (the ordering is not indicated)."
photo
contact	I				I
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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	?!Σ				?!Σ				Elements differ in short: "Extensions that cannot be ignored" "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." "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
name
telecom
address
gender
organization	I				I
period
animal	?!Σ								Removed this element
communication	S				S				Elements differ in short: "A list of Languages which may be used to communicate with the patient about his or her health" "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." "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." "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." "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."
id									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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	?!Σ				?!Σ				Elements differ in short: "Extensions that cannot be ignored" "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." "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	S				S
preferred
generalPractitioner									Elements differ in comments: "This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disablity setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources." "This may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources. Multiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a "fly-in/fly-out" worker that has the onsite GP also included with his home GP to remain aware of medical issues. Jurisdictions may decide that they can profile this down to 1 if desired, or 1 per type."
managingOrganization	Σ				Σ
link	?!Σ				?!Σ				Elements differ in comments: "There is no assumption that linked patient records have mutual links. This element is labelled as a modifier because it may not be the main Patient resource, and the referenced patient should be used instead of this Patient record. This is when the link.type value is 'replaced-by'." "There is no assumption that linked patient records have mutual links." 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." "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									Elements differ in short: "xml:id (or equivalent in JSON)" "Unique id for inter-element referencing"
extension			Extension				Extension		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." "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	?!Σ				?!Σ				Elements differ in short: "Extensions that cannot be ignored" "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." "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	Σ				Σ
type	Σ				Σ				Elements differ in short: "replaced-by | replaces | refer | seealso - type of link" "replaced-by | replaces | refer | seealso"
Documentation for this format