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

Left:Argonaut Procedure Profile (http://fhir.org/guides/argonaut/StructureDefinition/argo-procedure)
Right:US Core Procedure Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure)

Messages

ErrorStructureDefinition.urlValues for url differ: 'http://fhir.org/guides/argonaut/StructureDefinition/argo-procedure' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure'
InformationStructureDefinition.nameValues for name differ: 'Argonaut Procedure Profile' vs 'USCoreProcedureProfile'
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 Procedure Profile' vs 'An action that is being or was performed on a patient'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs '\-'
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.definitionValues for definition differ: '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).' vs '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.'
InformationStructureDefinition.requirementsValues for requirements differ: 'Need to allow connection to a wider workflow.' vs 'Allows identification of the procedure as it is known by various participating systems and in a way that remains consistent across servers.'
InformationStructureDefinition.shortValues for short differ: 'in-progress | aborted | completed | entered-in-error' vs 'preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown'
InformationStructureDefinition.definitionValues for definition differ: 'A code specifying the state of the procedure. Generally this will be in-progress or completed state.' vs 'A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.'
ErrorProcedure.statusUnable to resolve left value set http://hl7.org/fhir/ValueSet/procedure-status at Procedure.status
InformationStructureDefinition.shortValues for short differ: 'SNOMED-CT | ICD-10 | CPT-4' vs 'Identification of the procedure'
InformationStructureDefinition.definitionValues for definition differ: 'Limited to 'real' people rather than equipment.' vs 'Limited to 'real' people rather than equipment.'
InformationStructureDefinition.shortValues for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
InformationStructureDefinition.definitionValues for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
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 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.' vs '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.'
InformationStructureDefinition.shortValues for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs '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).'
InformationProcedure.performer.actorElement minimum cardinalities differ: '0' vs '1'
InformationStructureDefinition.shortValues for short differ: 'Date/Period the procedure was performed' vs 'When the procedure was performed'
InformationStructureDefinition.definitionValues for definition differ: 'The date(time)/period over which 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.' vs '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.'
InformationProcedure.performed[x]Element minimum cardinalities differ: '1' vs '0'
InformationStructureDefinition.shortValues for short differ: 'The encounter associated with the procedure' vs 'Encounter associated with the procedure'
InformationStructureDefinition.definitionValues for definition differ: 'The encounter during which the procedure was performed.' vs 'The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.'
WarningProcedure.encounterElements differ in definition for mustSupport: 'false' vs 'true'
InformationStructureDefinition.definitionValues for definition differ: 'The outcome of the procedure - did it resolve reasons for the procedure being performed?' vs 'The outcome of the procedure - did it resolve the reasons for the procedure being performed?'
InformationStructureDefinition.definitionValues for definition differ: 'This could be a histology result, pathology report, surgical report, etc..' vs 'This could be a histology result, pathology report, surgical report, etc.'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs '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.'
InformationStructureDefinition.shortValues for short differ: 'Device changed in procedure' vs 'Manipulated, implanted, or removed device'
InformationStructureDefinition.shortValues for short differ: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
InformationStructureDefinition.definitionValues for definition differ: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
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 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.' vs '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.'
InformationStructureDefinition.shortValues for short differ: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
InformationStructureDefinition.definitionValues for definition differ: '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.' vs '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).'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/fhir/StructureDefinition/Procedure
      .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 Procedure Profile is based upon the core FHIR Procedure Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 'Procedures' requirements. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. 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 Procedure Profile is based upon the core FHIR Procedure Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 'Procedures' requirements. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. 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 Procedure ProfileUSCoreProcedureProfile
          • Values Differ
          .publisherArgonaut ProjectHL7 International / Cross-Group Projects
          • Values Differ
          .purpose
            .statusdraftactive
            • Values Differ
            .titleUS Core Procedure Profile
            • Added the item 'US Core Procedure Profile'
            .typeProcedure
              .urlhttp://fhir.org/guides/argonaut/StructureDefinition/argo-procedurehttp://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure
              • 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
              .. Procedure C0..*ProcedureArgonaut Procedure Profile
              pro-1: Reason not performed is only permitted if notPerformed indicator is true
              C0..*ProcedureAn action that is being or was performed on a patient
              us-core-7: Performed SHALL be present if the status is 'completed' or 'in-progress'
                ... 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..*IdentifierExternal Identifiers for this procedure
                                Σ0..*IdentifierExternal Identifiers for this procedure
                                  ... subject S1..1Reference(Argonaut Patient Profile)Who the procedure was performed onSΣ1..1Reference(US Core Patient Profile S | Group)Who the procedure was performed on
                                    ... status ?!S1..1codein-progress | aborted | completed | entered-in-error
                                    Binding: ?? (required)
                                    ?!SΣC1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
                                    Binding: ?? (required)
                                    • Unable to resolve left value set http://hl7.org/fhir/ValueSet/procedure-status at Procedure.status
                                    ... category Σ0..1CodeableConceptClassification of the procedure
                                    Binding: ?? (example): A code that classifies a procedure for searching, sorting and display purposes.

                                    Σ0..1CodeableConceptClassification of the procedure
                                    Binding: ?? (example): A code that classifies a procedure for searching, sorting and display purposes.

                                      ... code S1..1CodeableConceptSNOMED-CT | ICD-10 | CPT-4
                                      Binding: ?? (extensible): Codes describing the Procedure Type

                                      Additional BindingsPurpose
                                      ??Max Binding
                                      SΣ1..1CodeableConceptIdentification of the procedure
                                      Binding: ?? (extensible): Codes describing the type of Procedure

                                        ... notPerformed ?!0..1booleanTrue if procedure was not performed as scheduled
                                        • Removed this element
                                        ... reasonNotPerformed C0..*CodeableConceptReason procedure was not performed
                                        Binding: ?? (example): A code that identifies the reason a procedure was not performed.


                                        • Removed this element
                                        ... bodySite Σ0..*CodeableConceptTarget body sites
                                        Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                        Σ0..*CodeableConceptTarget body sites
                                        Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                          ... reason[x] Σ0..1CodeableConcept, Reference(Condition)Reason procedure performed
                                          Binding: ?? (example): A code that identifies the reason a procedure is required.

                                          • Removed this element
                                          ... performer Σ0..*BackboneElementThe people who performed the procedure
                                          Σ0..*BackboneElementThe people who performed the procedure
                                            .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                                              .... 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 even if unrecognized
                                                  .... actor Σ0..1Reference(Practitioner | Organization | Patient | RelatedPerson)The reference to the practitionerΣ1..1Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)The reference to the practitioner
                                                  • Element minimum cardinalities differ: '0' vs '1'
                                                  .... role Σ0..1CodeableConceptThe role the actor was in
                                                  Binding: ?? (example): A code that identifies the role of a performer of the procedure.

                                                  • Removed this element
                                                  .... function Σ0..1CodeableConceptType of performance
                                                  Binding: ?? (example): A code that identifies the role of a performer of the procedure.

                                                  • Added this element
                                                  .... onBehalfOf 0..1Reference(Organization)Organization the device or practitioner was acting for
                                                  • Added this element
                                                  ... performed[x] S1..1dateTime, PeriodDate/Period the procedure was performedSΣC0..1dateTime S, Period, string, Age, RangeWhen the procedure was performed
                                                  • Element minimum cardinalities differ: '1' vs '0'
                                                  ... encounter Σ0..1Reference(Encounter)The encounter associated with the procedureSΣ0..1Reference(US Core Encounter Profile)Encounter associated with the procedure
                                                  • Elements differ in definition for mustSupport: 'false' vs 'true'
                                                  ... location Σ0..1Reference(Location)Where the procedure happenedΣ0..1Reference(Location)Where the procedure happened
                                                    ... outcome Σ0..1CodeableConceptThe result of procedure
                                                    Binding: ?? (example): An outcome of a procedure - whether it was resolved or otherwise.

                                                    Σ0..1CodeableConceptThe result of procedure
                                                    Binding: ?? (example): An outcome of a procedure - whether it was resolved or otherwise.

                                                      ... report 0..*Reference(DiagnosticReport)Any report resulting from the procedure
                                                      0..*Reference(DiagnosticReport | DocumentReference | Composition)Any report resulting from the procedure
                                                        ... complication 0..*CodeableConceptComplication following the procedure
                                                        Binding: ?? (example): Codes describing complications that resulted from a procedure.


                                                        0..*CodeableConceptComplication following the procedure
                                                        Binding: ?? (example): Codes describing complications that resulted from a procedure.


                                                          ... followUp 0..*CodeableConceptInstructions for follow up
                                                          Binding: ?? (example): Specific follow up required for a procedure e.g. removal of sutures.


                                                          0..*CodeableConceptInstructions for follow up
                                                          Binding: ?? (example): Specific follow up required for a procedure e.g. removal of sutures.


                                                            ... request 0..1Reference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest)A request for this procedure
                                                            • Removed this element
                                                            ... notes 0..*AnnotationAdditional information about the procedure
                                                            • Removed this element
                                                            ... focalDevice 0..*BackboneElementDevice changed in procedure
                                                            0..*BackboneElementManipulated, implanted, or removed device
                                                              .... id 0..1idxml:id (or equivalent in JSON)0..1stringUnique id for inter-element referencing
                                                                .... 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 even if unrecognized
                                                                    .... action 0..1CodeableConceptKind of change to device
                                                                    Binding: ?? (required): A kind of change that happened to the device during the procedure.

                                                                    0..1CodeableConceptKind of change to device
                                                                    Binding: ?? (preferred): A kind of change that happened to the device during the procedure.

                                                                      .... manipulated 1..1Reference(Device)Device that was changed1..1Reference(Device)Device that was changed
                                                                        ... used 0..*Reference(Device | Medication | Substance)Items used during procedure
                                                                        • Removed this element
                                                                        ... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
                                                                        • Added this element
                                                                        ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                                                        • Added this element
                                                                        ... basedOn Σ0..*Reference(US Core CarePlan Profile | US Core ServiceRequest Profile)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: A request for this procedure
                                                                        • Added this element
                                                                        ... partOf Σ0..*Reference(Procedure | Observation | MedicationAdministration)Part of referenced event
                                                                        • Added this element
                                                                        ... statusReason Σ0..1CodeableConceptReason for current status
                                                                        Binding: ?? (example): A code that identifies the reason a procedure was not performed.

                                                                        • Added this element
                                                                        ... recorder Σ0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)Who recorded the procedure
                                                                        • Added this element
                                                                        ... asserter Σ0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)Person who asserts this procedure
                                                                        • Added this element
                                                                        ... reasonCode Σ0..*CodeableConcept𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: Coded reason procedure performed
                                                                        Binding: ?? (extensible)
                                                                        • Added this element
                                                                        ... reasonReference Σ0..*Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference)𝗔𝗗𝗗𝗜𝗧𝗜𝗢𝗡𝗔𝗟 𝗨𝗦𝗖𝗗𝗜: US Core Profile justifying the reason procedure performed
                                                                        • Added this element
                                                                        ... complicationDetail 0..*Reference(Condition)A condition that is a result of the procedure
                                                                        • Added this element
                                                                        ... note 0..*AnnotationAdditional information about the procedure
                                                                        • Added this element
                                                                        ... usedReference 0..*Reference(Device | Medication | Substance)Items used during procedure
                                                                        • Added this element
                                                                        ... usedCode 0..*CodeableConceptCoded items used during the procedure
                                                                        Binding: ?? (example): Codes describing items used during a procedure.


                                                                        • Added this element

                                                                        doco Documentation for this format