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

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Procedure	http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure	Values Differ
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 Death Certification	DeathCertification	Values Differ
publisher	Hi3 Solutions	Health Level Seven International	Values Differ
purpose
status	draft
title		VRDR Death Certification	Added the item 'VRDR Death Certification'
type	Procedure
url	http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Death-Certification
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
Procedure	I								Elements differ in definition: "An action that is or was performed on a patient. This can be a physical intervention like an operation, or less invasive like counseling or hypnotherapy." "The US Core Condition Profile is based upon the core FHIR Procedure Resource and created to meet the 2015 Edition Common Clinical Data Set 'Procedures' requirements."
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-347)." "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-346)." "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-Certification" (CONF:4393-348)." "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 definition: "This records identifiers associated with this procedure that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation)." "Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server." Elements differ in requirements: "Need to allow connection to a wider workflow." "Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers."
definition	Σ								Removed this element
basedOn	Σ				Σ
partOf	Σ				Σ				Elements differ in comments: "The MedicationAdministration has a partOf reference to Procedure, but this is not a circular reference. For a surgical procedure, the anesthesia related medicationAdministration is part of the procedure. For an IV medication administration, the procedure to insert the IV port is part of the medication administration." "The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration)."
status	?!Σ				?!SΣ				Elements differ in definition: "SHALL contain exactly one [1..1] status=""completed""(CONF:4393-355)." "A code specifying the state of the procedure. Generally, this will be the in-progress or completed state." Elements differ in comments: "The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid." "The "unknown" code is not to be used to convey other statuses. The "unknown" code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid." Elements differ in definition for mustSupport: "false" "true"
notDone	?!Σ								Removed this element
notDoneReason	ΣI								Removed this element
category	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] category=""103693007""(CONF:4393-349)." "A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure")."
code	Σ				SΣ				Elements differ in definition: "SHALL contain exactly one [1..1] code=""308646001""(CONF:4393-350)." "The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy")." Elements differ in definition for mustSupport: "false" "true" Elements differ in binding.description: "A code to identify a specific procedure ." "Codes describing the type of Procedure"
subject	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
context	Σ								Removed this element
performed[x]	Σ		(Slice Definition)		SΣ				Elements differ in short: "performed[x]" "certificationDatetime" Elements differ in definition: "SHALL contain exactly one [1..1] performed[x], where performed[x] is (CONF:4393-351)" "Estimated or actual date, date-time, period, or age when the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be captured." Elements differ in definition for mustSupport: "false" "true"
performer	Σ				Σ				Elements differ in short: "performer" "The people who performed the procedure" Elements differ in definition: "SHALL contain exactly one [1..1] performer="VRDR Certifier"(CONF:4393-352)." "Limited to "real" people rather than equipment."
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)."
role	Σ								Removed this element
actor	Σ				Σ				Elements differ in short: "actor" "The reference to the practitioner" Elements differ in definition: "This performer SHALL contain exactly one [1..1] actor="VRDR Certifier" (CONF:4393-353)." "The practitioner who was involved in the procedure."
onBehalfOf
function					Σ				Added this element
location	Σ				Σ
reasonCode	Σ				Σ				Elements differ in definition: "The coded reason why the procedure was performed. This may be coded entity of some type, or may simply be present as text." "The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text."
reasonReference	Σ				Σ				Elements differ in short: "Condition that is the reason the procedure performed" "The justification that the procedure was performed" Elements differ in definition: "The condition that is the reason why the procedure was performed." "The justification of why the procedure was performed." Elements differ in comments: "e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic." "It is possible for a procedure to be a reason (such as C-Section) for another procedure (such as an epidural). Other examples include endoscopy for dilatation and biopsy (a combination of diagnostic and therapeutic use). Use Procedure.reasonCode when a code sufficiently describes the reason. Use Procedure.reasonReference when referencing a resource, which allows more information to be conveyed, such as onset date. Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure."
bodySite	Σ				Σ
outcome	Σ				Σ				Elements differ in definition: "The outcome of the procedure - did it resolve reasons for the procedure being performed?" "The outcome of the procedure - did it resolve the reasons for the procedure being performed?"
report									Elements differ in definition: "This could be a histology result, pathology report, surgical report, etc.." "This could be a histology result, pathology report, surgical report, etc."
complication
complicationDetail									Elements differ in short: "A condition that is a result of the procedure" "A condition that is a result of the procedure" Elements differ in requirements: "This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure." "This is used to document a condition that is a result of the procedure, not the condition that was the reason for the procedure."
followUp									Elements differ in definition: "If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or could potentially be more complex in which case the CarePlan resource can be used." "If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used."
note									Elements differ in definition: "Any other notes about the procedure. E.g. the operative notes." "Any other notes and comments about the procedure."
focalDevice									Elements differ in short: "Device changed in procedure" "Manipulated, implanted, or removed device"
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)."
action
manipulated
usedReference
usedCode									Elements differ in binding.description: "Codes describing items used during a procedure" "Codes describing items used during a procedure."
instantiatesCanonical					Σ				Added this element
instantiatesUri					Σ				Added this element
statusReason					Σ				Added this element
encounter					Σ				Added this element
recorder					Σ				Added this element
asserter					Σ				Added this element
Documentation for this format