Profile Comparison between http://hl7.org/cda/us/ccda/StructureDefinition/PlannedProcedure vs http://hl7.org/cda/us/ccda/StructureDefinition/PlannedProcedure

Left:Planned Procedure (http://hl7.org/cda/us/ccda/StructureDefinition/PlannedProcedure)
Right:Planned Procedure (http://hl7.org/cda/us/ccda/StructureDefinition/PlannedProcedure)

Messages

ErrorStructureDefinition.versionValues for version differ: '3.0.0-ballot' vs '3.0.0'
InformationStructureDefinition.dateValues for date differ: '2023-12-21T01:13:10+10:00' vs '2024-05-18T00:42:57-05:00'
InformationStructureDefinition.shortValues for short differ: 'If the Planned Intervention Procedure is a Social Determinant of Health Planned Intervention Procedure, the procedure code **SHOULD** be selected from ValueSet Social Determinant of Health Service Request (CONF:4515-32993)' vs '(USCDI) SDOH Interventions'
InformationStructureDefinition.commentValues for comment differ: 'SHALL contain exactly one [1..1] code (CONF:4515-31976).' vs 'This code SHALL contain exactly one [1..1] @code, which SHOULD be selected from ValueSet US Core Procedure Codes urn:oid:2.16.840.1.113883.4.642.40.48.31 .'
InformationProcedure.codeExample/preferred bindings differ at Procedure.code using binding from PlannedProcedure
InformationProcedure.codeStructureDefinition PlannedProcedure has a constraint that is removed in PlannedProcedure and it is uncertain whether they are compatible (codeSystem = '2.16.840.1.113883.6.1' or codeSystem = '2.16.840.1.113883.6.96' or codeSystem = '2.16.840.1.113883.6.12' or codeSystem = '2.16.840.1.113883.6.4' or codeSystem = '2.16.840.1.113883.6.285' or codeSystem = '2.16.840.1.113883.6.13')

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/cda/stds/core/StructureDefinition/Procedure
      .copyright
        .date2023-12-21T01:13:10+10:002024-05-18T00:42:57-05:00
        • Values Differ
        .descriptionThis template represents planned alterations of the patient's physical condition. Examples of such procedures are tracheostomy, knee replacement, and craniectomy. The priority of the procedure to the patient and provider is communicated through Priority Preference. The effectiveTime indicates the time when the procedure is intended to take place and authorTime indicates when the documentation of the plan occurred. The Planned Procedure Template may also indicate the potential insurance coverage for the procedure. Planned Procedure Usage Note: Common practice in the industry has shown that Planned Procedure is the usually implemented CDA template for any type of intervention or procedure regardless of if the "immediate and primary outcome (post-condition) is the alteration of the physical condition of the patient", or not. As a result, it is recommended to use Planned Procedure when sending procedures also thought of as "interventions" such as "Home Environment Evaluation" or "Assessment of nutritional status".
          .experimental
            .fhirVersion5.0.0
              .jurisdiction
                ..jurisdiction[0]urn:iso:std:iso:3166#US
                  .kindlogical
                    .namePlannedProcedure
                      .publisherHealth Level Seven
                        .purpose
                          .statusdraft
                            .titlePlanned Procedure
                              .typehttp://hl7.org/cda/stds/core/StructureDefinition/Procedure
                                .urlhttp://hl7.org/cda/us/ccda/StructureDefinition/PlannedProcedure
                                  .version3.0.0-ballot3.0.0
                                  • Values Differ

                                  Structure

                                  NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                  .. Procedure C1..1ProcedureBase for all types and resources
                                  Instance of this type are validated by templateId
                                  Logical Container: ClinicalDocument (CDA Class)
                                  should-text-ref-value: SHOULD contain text/reference/@value
                                  should-effectiveTime: SHOULD contain effectiveTime
                                  should-author: SHOULD contain author
                                  C1..1ProcedureBase for all types and resources
                                  Instance of this type are validated by templateId
                                  Logical Container: ClinicalDocument (CDA Class)
                                  should-text-ref-value: SHOULD contain text/reference/@value
                                  should-effectiveTime: SHOULD contain effectiveTime
                                  should-author: SHOULD contain author
                                    ... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                      ... realmCode 0..*CS0..*CS
                                        ... typeId 0..1II0..1II
                                          .... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                            .... assigningAuthorityName 0..1??0..1??
                                              .... displayable 0..1??0..1??
                                                .... root 1..1??, ??, ??Fixed Value: 2.16.840.1.113883.1.31..1??, ??, ??Fixed Value: 2.16.840.1.113883.1.3
                                                  .... st-simple 1..1stringPrimitive Type string
                                                  URL: http://hl7.org/cda/stds/core/StructureDefinition/st-simple
                                                  1..1stringPrimitive Type string
                                                  URL: http://hl7.org/cda/stds/core/StructureDefinition/st-simple
                                                    ... Slices for templateId 1..*IISlice: Unordered, Open by value:root, value:extension
                                                    1..*IISlice: Unordered, Open by value:root, value:extension
                                                      ... classCode 1..1??Binding: ?? (required)
                                                      Fixed Value: PROC
                                                      1..1??Binding: ?? (required)
                                                      Fixed Value: PROC
                                                        ... moodCode 1..1??Binding: ?? (required)1..1??Binding: ?? (required)
                                                          ... id 1..*II1..*II
                                                            ... code C1..1CDIf the Planned Intervention Procedure is a Social Determinant of Health Planned Intervention Procedure, the procedure code **SHOULD** be selected from ValueSet Social Determinant of Health Service Request (CONF:4515-32993)
                                                            Binding: ?? (preferred)
                                                            4515-31977: This @code SHOULD be selected from LOINC (CodeSystem: 2.16.840.1.113883.6.1) or SNOMED CT (CodeSystem: 2.16.840.1.113883.6.96) or CPT (CodeSystem: 2.16.840.1.113883.6.12) or ICD-10-PCS (CodeSystem: 2.16.840.1.113883.6.4) or HCPCS (Code System: 2.16.840.1.113883.6.285) or CDT-2 (Code System: 2.16.840.1.113883.6.13) (CONF:4515-31977).
                                                            1..1CD(USCDI) SDOH Interventions
                                                            Binding: ?? (preferred)
                                                            Additional BindingsPurposeDocumentation
                                                            ??Preferred Binding
                                                            For Social Determinant of Planned Intervention Procedure
                                                            • Example/preferred bindings differ at Procedure.code using binding from PlannedProcedure
                                                            • StructureDefinition PlannedProcedure has a constraint that is removed in PlannedProcedure and it is uncertain whether they are compatible (codeSystem = '2.16.840.1.113883.6.1' or codeSystem = '2.16.840.1.113883.6.96' or codeSystem = '2.16.840.1.113883.6.12' or codeSystem = '2.16.840.1.113883.6.4' or codeSystem = '2.16.840.1.113883.6.285' or codeSystem = '2.16.840.1.113883.6.13')
                                                            ... negationInd 0..1??0..1??
                                                              ... text 0..1EDSHOULD reference the portion of section narrative text corresponding to this entry0..1EDSHOULD reference the portion of section narrative text corresponding to this entry
                                                                .... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                  .... compression 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                    .... integrityCheck 0..1??0..1??
                                                                      .... integrityCheckAlgorithm 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                        .... language 0..1??0..1??
                                                                          .... mediaType 0..1??Binding: ?? (example)0..1??Binding: ?? (example)
                                                                            .... representation 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                              .... xmlText 0..1??Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.0..1??Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
                                                                                .... reference C0..1TELvalue-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrativeC0..1TELvalue-starts-octothorpe: If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative
                                                                                  .... thumbnail 0..1ED0..1ED
                                                                                    ... statusCode 1..1CSBinding: ?? (required)1..1CSBinding: ?? (required)
                                                                                      .... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                                        .... code 1..1??Fixed Value: active1..1??Fixed Value: active
                                                                                          .... codeSystem 0..00..0
                                                                                            .... codeSystemName 0..00..0
                                                                                              .... codeSystemVersion 0..00..0
                                                                                                .... displayName 0..00..0
                                                                                                  .... sdtcValueSet 0..1??XML: valueSet (urn:hl7-org:sdtc)0..1??XML: valueSet (urn:hl7-org:sdtc)
                                                                                                    .... sdtcValueSetVersion 0..1??XML: valueSetVersion (urn:hl7-org:sdtc)0..1??XML: valueSetVersion (urn:hl7-org:sdtc)
                                                                                                      .... originalText 0..00..0
                                                                                                        .... qualifier 0..00..0
                                                                                                          .... translation 0..00..0
                                                                                                            ... effectiveTime 0..1IVL_TSThe effectiveTime in a planned procedure represents the time that the procedure should occur.0..1IVL_TSThe effectiveTime in a planned procedure represents the time that the procedure should occur.
                                                                                                              ... priorityCode 0..1CEBinding: ?? (example)0..1CEBinding: ?? (example)
                                                                                                                ... languageCode 0..1CSBinding: ?? (required)0..1CSBinding: ?? (required)
                                                                                                                  ... methodCode 0..*CEIn a planned procedure the provider may suggest that a procedure should be performed using a particular method. MethodCode *SHALL NOT* conflict with the method inherent in Procedure/code.
                                                                                                                  0..*CEIn a planned procedure the provider may suggest that a procedure should be performed using a particular method. MethodCode *SHALL NOT* conflict with the method inherent in Procedure/code.
                                                                                                                    ... approachSiteCode 0..*CD0..*CD
                                                                                                                      ... targetSiteCode 0..*CDThe targetSiteCode is used to identify the part of the body of concern for the planned procedure.
                                                                                                                      Binding: ?? (required)
                                                                                                                      0..*CDThe targetSiteCode is used to identify the part of the body of concern for the planned procedure.
                                                                                                                      Binding: ?? (required)
                                                                                                                        ... subject 0..1Subject0..1Subject
                                                                                                                          ... specimen 0..*Specimen0..*Specimen
                                                                                                                            ... performer 0..*Performer2The clinician who is expected to perform the procedure could be identified using procedure/performer.
                                                                                                                            0..*Performer2The clinician who is expected to perform the procedure could be identified using procedure/performer.
                                                                                                                              ... author 0..1??The author in a planned procedure represents the clinician who is requesting or planning the procedure.
                                                                                                                              0..1??The author in a planned procedure represents the clinician who is requesting or planning the procedure.
                                                                                                                                ... informant 0..*Informant0..*Informant
                                                                                                                                  ... participant 0..*Participant20..*Participant2
                                                                                                                                    ... Slices for entryRelationship 0..*EntryRelationshipSlice: Unordered, Open by profile:act, profile:observation
                                                                                                                                    0..*EntryRelationshipSlice: Unordered, Open by profile:act, profile:observation
                                                                                                                                      ... reference 0..*Reference0..*Reference
                                                                                                                                        ... precondition 0..*Precondition0..*Precondition
                                                                                                                                          ... sdtcPrecondition2 0..*Precondition2XML: precondition2 (urn:hl7-org:sdtc)
                                                                                                                                          0..*Precondition2XML: precondition2 (urn:hl7-org:sdtc)
                                                                                                                                            ... sdtcInFulfillmentOf1 0..*InFulfillmentOf1XML: inFulfillmentOf1 (urn:hl7-org:sdtc)
                                                                                                                                            0..*InFulfillmentOf1XML: inFulfillmentOf1 (urn:hl7-org:sdtc)

                                                                                                                                              doco Documentation for this format