Skip to content

Procedure Alternatives is Invalid at a base CDA level #2

@benjaminflessner

Description

@benjaminflessner

https://build.fhir.org/ig/HL7/CDA-Examples/Binary-procedures-procedure-alternatives.html

This gives examples of using moodCode=PRP on the organizer, and classCode=SUBST on the procedure.

Snippet from example
      <!-- This entryRelationship contains an organizer listing alternative planned procedures...
         The options below should be read as: CPT 44960 OR 44970 -->
      <entryRelationship typeCode="REFR">
        <organizer classCode="CLUSTER" moodCode="PRP">
          <!-- "PRP" = proposal
             A non-mandated intent to perform an act. Used to record intents that are explicitly not Orders.
             Professional responsibility for the 'proposal' may or may not be present. -->
          <!-- Implementers may include an organizer/code here with a value "alternative procedure options,"
             although we were unable to find an appropriate one.  -->
          
          <statusCode code="active" />
          
          <!-- First alternative -->
          <component>
            <procedure classCode="SUBST" moodCode="PRP">
              <!-- "SUBST" = substitution
                 Indicates that the subject Act has undergone or should undergo substitution of a type indicated by Act.code. -->
              <code code="44960" codeSystem="2.16.840.1.113883.6.12" codeSystemName="CPT-4"
                displayName="Appendectomy; for ruptured appendix with abscess or generalized peritonitis" />
            </procedure>
          </component>

However, in the base CDA spec, Organizer.moodCode is fixed to EVN, and Procedure.classCode is fixed to PROC.

This example needs to be fully re-done, or else withdrawn as an invalid example.

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalid exampleThe example has a validation problem or uncovers a new issue with a template

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions