Profile Comparison between http://fhir.org/guides/argonaut/StructureDefinition/argo-device vs http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device

Left:Argonaut Device Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-device)
Right:US Core Implantable Device Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-device' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device'
InformationStructureDefinition.nameValues for name differ: 'Argonaut Device Profile' vs 'USCoreImplantableDeviceProfile'
InformationStructureDefinition.statusValues for status differ: 'draft' vs 'active'
InformationStructureDefinition.dateValues for date differ: '2016-10-18T00:00:00+11:00' vs '2023-10-17'
InformationStructureDefinition.publisherValues for publisher differ: 'Argonaut Project' vs 'HL7 International / Cross-Group Projects'
InformationStructureDefinition.jurisdictionAdded the item 'urn:iso:std:iso:3166#US'
WarningStructureDefinition.fhirVersionValues for fhirVersion differ: '1.0.2' vs '4.0.1'
InformationStructureDefinition.shortValues for short differ: 'Argonaut Device Profile' vs 'Item used in healthcare'
InformationStructureDefinition.definitionValues for definition differ: 'This resource identifies an instance of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. Medical devices includes durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc.' vs '\-'
InformationDeviceStructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.contained.empty())
InformationDeviceStructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
InformationDeviceStructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
InformationDeviceStructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
InformationDeviceStructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (text.`div`.exists())
InformationStructureDefinition.commentValues for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
InformationStructureDefinition.definitionValues for definition differ: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.'
InformationStructureDefinition.definitionValues for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
InformationStructureDefinition.commentValues for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
InformationStructureDefinition.commentValues for comment differ: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
InformationStructureDefinition.definitionValues for definition differ: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it 'clinically safe' for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
InformationStructureDefinition.commentValues for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.'
InformationStructureDefinition.commentValues for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
InformationStructureDefinition.shortValues for short differ: 'Additional Content defined by implementations' vs 'Additional content defined by implementations'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs '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.'
InformationStructureDefinition.definitionValues for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
InformationStructureDefinition.shortValues for short differ: 'Instance id from manufacturer, owner, and others' vs 'Instance identifier'
InformationStructureDefinition.definitionValues for definition differ: 'Unique instance identifiers assigned to a device by organizations like manufacturers or owners. If the identifier identifies the type of device, Device.type should be used.' vs 'Unique instance identifiers assigned to a device by manufacturers other organizations or owners.'
InformationStructureDefinition.commentValues for comment differ: 'Often fixed to the device as a barcode and may include names given to the device in local usage. Note that some of the barcodes affixed to the device identify its type, not its instance. For the FDA mandated Unique Device Identifier (UDI) use the Device.udi element.' vs 'The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.'
InformationStructureDefinition.shortValues for short differ: 'What kind of device this is' vs 'The kind or type of device'
InformationStructureDefinition.definitionValues for definition differ: 'Code or identifier to identify a kind of device.' vs 'The kind or type of device.'
InformationStructureDefinition.shortValues for short differ: 'available | not-available | entered-in-error' vs 'active | inactive | entered-in-error | unknown'
ErrorDevice.statusUnable to resolve left value set http://hl7.org/fhir/ValueSet/devicestatus at Device.status
InformationStructureDefinition.shortValues for short differ: 'Version number (i.e. software)' vs 'The actual design of the device or software version running on the device'
InformationStructureDefinition.definitionValues for definition differ: 'The version of the device, if the device has multiple releases under the same model, or if the device is software or carries firmware.' vs 'The actual design of the device or software version running on the device.'
InformationDevice.versionElement maximum cardinalities differ: '1' vs '2147483647'
InformationStructureDefinition.shortValues for short differ: 'Manufacture date' vs 'Date when the device was made'
WarningDevice.manufactureDateElements differ in definition for mustSupport: 'false' vs 'true'
WarningDevice.lotNumberElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.shortValues for short differ: 'Where the resource is found' vs 'Where the device is found'
InformationStructureDefinition.shortValues for short differ: 'If the resource is affixed to a person' vs 'Patient to whom Device is affixed'
InformationStructureDefinition.definitionValues for definition differ: 'Patient information, if the resource is affixed to a person.' vs 'Patient information, If the device is affixed to a person.'
InformationStructureDefinition.commentValues for comment differ: 'If the device is running a FHIR server, the network address should be the root URL from which a conformance statement may be retrieved.' vs 'If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Device
      .copyrightUsed by permission of HL7 International, all rights reserved Creative Commons License
      • Added the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
      .date2016-10-18T00:00:00+11:002023-10-17
      • Values Differ
      .descriptionThe US Core Implantable Device Profile is based upon the core FHIR Device Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 *Unique Device Identifier(s) for a Patient's Implantable Device(s)* requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Device resource to record, search, and fetch UDI information associated with a patient's implantable device(s). It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
      • Added the item 'The US Core Implantable Device Profile is based upon the core FHIR Device Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 *Unique Device Identifier(s) for a Patient's Implantable Device(s)* requirements. To promote interoperability and adoption through common implementation, this profile sets minimum expectations for the Device resource to record, search, and fetch UDI information associated with a patient's implantable device(s). It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.'
      .experimentalfalse
      • Added the item 'false'
      .fhirVersion1.0.24.0.1
      • Values Differ
      .jurisdiction
        ..jurisdiction[0]urn:iso:std:iso:3166#US
        • Added the item 'urn:iso:std:iso:3166#US'
        .kindresource
          .nameArgonaut Device ProfileUSCoreImplantableDeviceProfile
          • Values Differ
          .publisherArgonaut ProjectHL7 International / Cross-Group Projects
          • Values Differ
          .purpose
            .statusdraftactive
            • Values Differ
            .titleUS Core Implantable Device Profile
            • Added the item 'US Core Implantable Device Profile'
            .typeDevice
              .urlhttp://fhir.org/guides/argonaut/StructureDefinition/argo-devicehttp://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device
              • Values Differ
              .version7.0.0-ballot
              • Added the item '7.0.0-ballot'

              Structure

              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
              .. Device 0..*DeviceArgonaut Device Profile
              0..*DeviceItem used in healthcare
              • StructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.contained.empty())
              • StructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty())
              • StructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.meta.versionId.empty() and contained.meta.lastUpdated.empty())
              • StructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (contained.meta.security.empty())
              • StructureDefinition USCoreImplantableDeviceProfile has added constraint that is not found in Argonaut Device Profile and it is uncertain whether they are compatible (text.`div`.exists())
              ... id Σ0..1idLogical id of this artifactΣ0..1idLogical id of this artifact
                ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                    ... language 0..1codeLanguage of the resource content
                    Binding: ?? (required): A human language.

                    0..1codeLanguage of the resource content
                    Binding: ?? (preferred): A human language.

                    Additional BindingsPurpose
                    ??Max Binding
                      ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                        ... contained 0..*ResourceContained, inline Resources
                        0..*ResourceContained, inline Resources
                          ... extension 0..*ExtensionAdditional Content defined by implementations
                          0..*ExtensionAdditional content defined by implementations
                            ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                            ?!0..*ExtensionExtensions that cannot be ignored
                              ... identifier 0..*IdentifierInstance id from manufacturer, owner, and others
                              0..*IdentifierInstance identifier
                                ... type S1..1CodeableConceptWhat kind of device this is
                                Binding: ?? (extensible): Codes to identify medical devices

                                S1..1CodeableConceptThe kind or type of device
                                Binding: ?? (extensible): Codes to identify medical devices

                                  ... note 0..*AnnotationDevice notes and comments
                                  0..*AnnotationDevice notes and comments
                                    ... status ?!Σ0..1codeavailable | not-available | entered-in-error
                                    Binding: ?? (required): The availability status of the device.

                                    ?!Σ0..1codeactive | inactive | entered-in-error | unknown
                                    Binding: ?? (required): The availability status of the device.

                                    • Unable to resolve left value set http://hl7.org/fhir/ValueSet/devicestatus at Device.status
                                    ... manufacturer 0..1stringName of device manufacturer0..1stringName of device manufacturer
                                      ... model 0..1stringModel id assigned by the manufacturer
                                      • Removed this element
                                      ... version 0..1stringVersion number (i.e. software)0..*BackboneElementThe actual design of the device or software version running on the device
                                      • Element maximum cardinalities differ: '1' vs '2147483647'
                                      .... id 0..1stringUnique id for inter-element referencing
                                      • Added this element
                                      .... extension 0..*ExtensionAdditional content defined by implementations
                                      • Added this element
                                      .... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
                                      • Added this element
                                      .... type 0..1CodeableConceptThe type of the device version
                                      • Added this element
                                      .... component 0..1IdentifierA single component of the device version
                                      • Added this element
                                      .... value 1..1stringThe version text
                                      • Added this element
                                      ... manufactureDate 0..1dateTimeManufacture dateS0..1dateTimeDate when the device was made
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      ... expiry 0..1dateTimeDate and time of expiry of this device (if applicable)
                                      • Removed this element
                                      ... udi S1..1stringFDA mandated Unique Device Identifier
                                      • Removed this element
                                      ... lotNumber 0..1stringLot number of manufactureS0..1stringLot number of manufacture
                                      • Elements differ in definition for mustSupport: 'false' vs 'true'
                                      ... owner 0..1Reference(Organization)Organization responsible for device0..1Reference(Organization)Organization responsible for device
                                        ... location 0..1Reference(Location)Where the resource is found0..1Reference(Location)Where the device is found
                                          ... patient S1..1Reference(Argonaut Patient Profile)If the resource is affixed to a personS1..1Reference(US Core Patient Profile)Patient to whom Device is affixed
                                            ... contact 0..*ContactPointDetails for human/organization for support
                                            0..*ContactPointDetails for human/organization for support
                                              ... url 0..1uriNetwork address to contact device0..1uriNetwork address to contact device
                                                ... definition 0..1Reference(DeviceDefinition)The reference to the definition for the device
                                                • Added this element
                                                ... udiCarrier SΣ0..1BackboneElementUnique Device Identifier (UDI) Barcode string
                                                • Added this element
                                                ... statusReason 0..*CodeableConceptonline | paused | standby | offline | not-ready | transduc-discon | hw-discon | off
                                                Binding: ?? (extensible): The availability status reason of the device.


                                                • Added this element
                                                ... distinctIdentifier S0..1stringThe distinct identification string
                                                • Added this element
                                                ... expirationDate S0..1dateTimeDate and time of expiry of this device (if applicable)
                                                • Added this element
                                                ... serialNumber S0..1stringSerial number assigned by the manufacturer
                                                • Added this element
                                                ... deviceName 0..*BackboneElementThe name of the device as given by the manufacturer
                                                • Added this element
                                                ... modelNumber 0..1stringThe model number for the device
                                                • Added this element
                                                ... partNumber 0..1stringThe part number of the device
                                                • Added this element
                                                ... specialization 0..*BackboneElementThe capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication
                                                • Added this element
                                                ... property 0..*BackboneElementThe actual configuration settings of a device as it actually operates, e.g., regulation status, time properties
                                                • Added this element
                                                ... safety Σ0..*CodeableConceptSafety Characteristics of Device
                                                • Added this element
                                                ... parent 0..1Reference(Device)The parent device
                                                • Added this element

                                                doco Documentation for this format