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

Messages

Metadata

Name	Value		Comments
abstract	false
baseDefinition	http://hl7.org/fhir/StructureDefinition/Location	http://hl7.org/fhir/us/core/StructureDefinition/us-core-location	Values Differ
copyright
date	2019-03-27T07:24:20+11:00	2020-05-13	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 Injury Location	InjuryLocation	Values Differ
publisher	Hi3 Solutions	Health Level Seven International	Values Differ
purpose
status	draft
title		VRDR Injury Location	Added the item 'VRDR Injury Location'
type	Location
url	http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Injury-Location
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
Location									Elements differ in definition: "Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated." "Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated."
id	Σ				Σ				Elements differ in definition: "MAY contain zero or one [0..1] id (CONF:4393-276)." "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-275)." "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-Injury-Location" (CONF:4393-277)." "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	Σ				Σ
status	?!Σ				?!SΣ				Elements differ in definition for mustSupport: "false" "true"
operationalStatus	Σ				Σ				Elements differ in definition: "The Operational status covers operation values most relevant to beds (but can also apply to rooms/units/chair/etc such as an isolation unit/dialisys chair). This typically covers concepts such as contamination, housekeeping and other activities like maintenance." "The operational status covers operation values most relevant to beds (but can also apply to rooms/units/chairs/etc. such as an isolation unit/dialysis chair). This typically covers concepts such as contamination, housekeeping, and other activities like maintenance." Example/preferred bindings differ at Location.operationalStatus using binding from VRDR Injury Location Elements differ in binding.description: "The operational status if the location (where typically a bed/room)" "The operational status if the location (where typically a bed/room)."
name	Σ				SΣ				Elements differ in definition: "SHALL contain exactly one [1..1] name (CONF:4393-280)." "Name of the location as used by humans. Does not need to be unique." Elements differ in comments: "If the name of an location changes, consider putting the old name in the alias column so that it can still be located through searches." "If the name of a location changes, consider putting the old name in the alias column so that it can still be located through searches." Elements differ in definition for mustSupport: "false" "true"
alias									Elements differ in short: "A list of alternate names that the location is known as, or was known as in the past" "A list of alternate names that the location is known as, or was known as, in the past" Elements differ in definition: "A list of alternate names that the location is known as, or was known as in the past." "A list of alternate names that the location is known as, or was known as, in the past."
description	Σ				Σ				Elements differ in definition: "SHALL contain exactly one [1..1] description (CONF:4393-279)." "Description of the Location, which helps in finding or referencing the place."
mode	?!Σ				Σ				Elements differ in comments: "This is labeled as a modifer because whether or not the location is a class of locations changes how it can be used and understood." "This is labeled as a modifier because whether or not the location is a class of locations changes how it can be used and understood."
type	Σ				Σ				Elements differ in short: "type" "Type of function performed" Elements differ in definition: "SHALL contain exactly one [1..1] type, which SHALL be selected from ValueSet v3-ServiceDeliveryLocationRoleType http://hl7.org/fhir/ValueSet/v3-ServiceDeliveryLocationRoleType (CONF:4393-282)." "Indicates the type of function performed at the location."
telecom					S				Elements differ in definition for mustSupport: "false" "true"
address					S				Elements differ in definition: "SHALL contain exactly one [1..1] address (CONF:4393-278)." "Physical location." Elements differ in comments: "This was kept as 0..1 as there is no use property on the address, so wouldn't be able to identify different address types." "Additional addresses should be recorded using another instance of the Location resource, or via the Organization." 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."
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	Σ				Σ
physicalType	Σ				Σ				Elements differ in short: "physicalType" "Physical form of the location" Elements differ in definition: "SHALL contain exactly one [1..1] physicalType, which SHALL be selected from ValueSet Location-physical-type http://hl7.org/fhir/ValueSet/Location-physical-type DYNAMIC (CONF:4393-281)." "Physical form of the location, e.g. building, room, vehicle, road."
position
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)."
longitude
latitude
altitude
managingOrganization	Σ				SΣ				Elements differ in definition for mustSupport: "false" "true"
partOf									Elements differ in short: "Another Location this one is physically part of" "Another Location this one is physically a part of" Elements differ in definition: "Another Location which this Location is physically part of." "Another Location of which this Location is physically a part of."
endpoint
hoursOfOperation									Added this element
availabilityExceptions									Added this element
Documentation for this format