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

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Composition
copyright
date	2019-03-27T07:24:20+11:00	2020-05-09	Values Differ
description		The Death Certificate profile is the body of the death certificate document. It builds upon the FHIR Composition resource.	Added the item 'The Death Certificate profile is the body of the death certificate document. It builds upon the FHIR Composition resource.'
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 Death Certificate	DeathCertificate	Values Differ
publisher	Hi3 Solutions	Health Level Seven International	Values Differ
purpose
status	draft
title		VRDR Death Certificate	Added the item 'VRDR Death Certificate'
type	Composition
url	http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Death-Certificate
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
Composition									Elements differ in definition: "A set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained." "A set of healthcare-related information that is assembled together into a single logical package that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. A Composition defines the structure and narrative content necessary for a document. However, a Composition alone does not constitute a document. Rather, the Composition must be the first entry in a Bundle where Bundle.type=document, and any other resources referenced from Composition must be included as subsequent entries in the Bundle (for example Patient, Practitioner, Encounter, etc.)."
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-364)." "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-363)." "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."
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."
versionId	Σ				Σ				Elements differ in definition: "The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted." "The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted."
lastUpdated	Σ				Σ				Elements differ in comments: "This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant." "This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read] interaction."
profile	Σ				Σ				Elements differ in short: "profile" "Profiles this resource claims to conform to" Elements differ in definition: "The meta, if present, SHALL contain exactly one [1..1] profile="http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Death-Certificate"(CONF:4393-365)." "A list of profiles (references to [StructureDefinition] resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url]."
security	Σ				Σ				Elements differ in comments: "The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored." "The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored."
tag	Σ				Σ				Elements differ in comments: "The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored." "The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored." Elements differ in binding.description: "Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"" "Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones"."
source					Σ				Added this element
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: "May be used to represent additional information that is not part of the basic definition of the resource. 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 resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension."
modifierExtension	?!				?!				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	Σ				Σ				Elements differ in short: "identifier" "Version-independent identifier for the Composition" Elements differ in definition: "SHALL contain exactly one [1..1] identifier (CONF:4393-374)." "A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time." Elements differ in comments: "See discussion in resource definition for how these relate." "Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate."
status	?!Σ				?!Σ				Elements differ in definition: "SHALL contain exactly one [1..1] status, which SHALL be selected from ValueSet CompositionStatus http://hl7.org/fhir/ValueSet/CompositionStatus DYNAMIC (CONF:4393-375)." "The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document." Elements differ in comments: "If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements. Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required." "If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements. Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required."
type	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] type="64297-5"(CONF:4393-377)." "Specifies the particular kind of composition (e.g. History and Physical, Discharge Summary, Progress Note). This usually equates to the purpose of making the composition."
class	Σ								Removed this element
subject	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] subject="VRDR Decedent"(CONF:4393-376)." "Who or what the composition is about. The composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure)."
encounter	Σ				Σ
date	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] date (CONF:4393-370)." "The composition editing time, when the composition was last logically changed by the author." Elements differ in requirements: "dateTime is used for tracking, organizing versions and searching." "dateTime is used for tracking, organizing versions and searching. Note that this is the time of *authoring*. When packaged in a document, [Bundle.timestamp] is the date of packaging."
author	Σ				Σ
title	Σ				Σ
confidentiality	?!Σ				Σ				Elements differ in comments: "The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not." "The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not."
attester	Σ								Elements differ in definition: "SHALL contain exactly one [1..1] attester=""legal""(CONF:4393-366)." "A participant who has attested to the accuracy of the composition/document."
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)."
mode	Σ
time	Σ
party	Σ
custodian	Σ				Σ
relatesTo	Σ
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)."
code	Σ
target[x]	Σ
event	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] event=""103693007""(CONF:4393-371)." "The clinical service, such as a colonoscopy or an appendectomy, being documented."
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)."
code	Σ				Σ
period	Σ				Σ
detail	Σ				Σ
section	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)."
title
code									Elements differ in comments: "The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code." "The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code."
text	I				I
mode	?!Σ								Elements differ in comments: "This element is labeled as a modifier because a change list must not be mis-understood as a complete list." "This element is labeled as a modifier because a change list must not be misunderstood as a complete list."
orderedBy
entry	I				I
emptyReason	I				I
section	I				I
author									Added this element
focus									Added this element
category					Σ				Added this element
Documentation for this format