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

Left:Notes Section (http://hl7.org/cda/us/ccda/StructureDefinition/NotesSection)
Right:Notes Section (http://hl7.org/cda/us/ccda/StructureDefinition/NotesSection)

Messages

InformationSection.typeIdStructureDefinition NotesSection has added constraint that is not found in NotesSection and it is uncertain whether they are compatible (root.exists() or nullFlavor.exists())
InformationSection.component.typeIdStructureDefinition NotesSection has added constraint that is not found in NotesSection and it is uncertain whether they are compatible (root.exists() or nullFlavor.exists())

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://hl7.org/cda/stds/core/StructureDefinition/Section
      .copyright
        .descriptionThe Notes Section allow for inclusion of clinical documentation which does not fit precisely within any other C-CDA section. Multiple Notes sections may be included in a document provided they each include different types of note content as indicated by a different section.code. The Notes Section SHOULD NOT be used in place of a more specific C-CDA section. For example, notes about procedure should be placed within the Procedures Section, not a Notes Section. When a Notes Section is present, Note Activity entries contain structured information about the note information allowing it to be more machine processable. The Notes Section allow for inclusion of clinical documentation which does not fit precisely within any other C-CDA section. Multiple Notes sections may be included in a document provided they each include different types of note content as indicated by a different section.code. The Notes Section SHOULD NOT be used in place of a more specific C-CDA section. For example, notes about procedure should be placed within the Procedures Section, not a Notes Section. When a Notes Section is present, Note Activity entries contain structured information about the note information allowing it to be more machine processable. #### Templates Used Although open templates may contain any valid CDA content, the following templates are specifically called out by this template: **Required Entries**: [NoteActivity](StructureDefinition-NoteActivity.html)
        • Values Differ
        .experimental
          .fhirVersion5.0.0
            .jurisdiction
              ..jurisdiction[0]urn:iso:std:iso:3166#US
                .kindlogical
                  .nameNotesSection
                    .publisherHealth Level Seven
                      .purpose
                        .statusdraft
                          .titleNotes Section
                            .typehttp://hl7.org/cda/stds/core/StructureDefinition/Section
                              .urlhttp://hl7.org/cda/us/ccda/StructureDefinition/NotesSection

                                Structure

                                NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.R TypeR Description & ConstraintsCommentsdoco
                                .. Section C1..1SectionBase for all types and resources
                                Instance of this type are validated by templateId
                                Logical Container: ClinicalDocument (CDA Class)
                                Constraints: shall-note-activity
                                C1..1SectionBase for all types and resources
                                Instance of this type are validated by templateId
                                Logical Container: ClinicalDocument (CDA Class)
                                Constraints: shall-note-activity
                                  ... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                    ... realmCode 0..*CS0..*CS
                                      ... typeId 0..1IIC0..1II
                                      • StructureDefinition NotesSection has added constraint that is not found in NotesSection and it is uncertain whether they are compatible (root.exists() or nullFlavor.exists())
                                      .... 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
                                              .... extension 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
                                                ... ID 0..1??0..1??
                                                  ... classCode 0..1??Binding: ?? (required)
                                                  Fixed Value: DOCSECT
                                                  0..1??Binding: ?? (required)
                                                  Fixed Value: DOCSECT
                                                    ... moodCode 0..1??Binding: ?? (required)
                                                    Fixed Value: EVN
                                                    0..1??Binding: ?? (required)
                                                    Fixed Value: EVN
                                                      ... id 0..1II0..1II
                                                        ... code 1..1CEBinding: ?? (preferred)1..1CEBinding: ?? (preferred)
                                                          .... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                            .... code 1..1??1..1??
                                                              .... codeSystem 1..1??, ??, ??Required Pattern: 2.16.840.1.113883.6.11..1??, ??, ??Required Pattern: 2.16.840.1.113883.6.1
                                                                .... codeSystemName 0..1??0..1??
                                                                  .... codeSystemVersion 0..1??0..1??
                                                                    .... displayName 0..1??0..1??
                                                                      .... 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..1ED0..1ED
                                                                            .... qualifier 0..00..0
                                                                              .... translation 0..*CD0..*CD
                                                                                ... title 1..1STThis title should reflect the kind of notes included in this section, corresponding to the code.1..1STThis title should reflect the kind of notes included in this section, corresponding to the code.
                                                                                  ... text 1..1xhtmlThe narrative SHOULD contain human-readable representations using standard CDA narrative markup of each note to ensure widest compatibility with receivers. While allowed by CDA, the use of renderMultiMedia elements, which contain a referencedObject attribute pointing to an observationMedia or regionOfInterest element in the discrete entries, is discouraged in Note Sections because rendering support for these elements is not widespread.1..1xhtmlThe narrative SHOULD contain human-readable representations using standard CDA narrative markup of each note to ensure widest compatibility with receivers. While allowed by CDA, the use of renderMultiMedia elements, which contain a referencedObject attribute pointing to an observationMedia or regionOfInterest element in the discrete entries, is discouraged in Note Sections because rendering support for these elements is not widespread.
                                                                                    ... confidentialityCode 0..1CE0..1CE
                                                                                      ... languageCode 0..1CSBinding: ?? (required)0..1CSBinding: ?? (required)
                                                                                        ... subject 0..1Subject0..1Subject
                                                                                          ... author 0..*Author0..*Author
                                                                                            ... informant 0..*Informant0..*Informant
                                                                                              ... Slices for entry 0..*EntrySlice: Unordered, Open by profile:act
                                                                                              0..*EntrySlice: Unordered, Open by profile:act
                                                                                                ... component 0..*InfrastructureRoot0..*InfrastructureRoot
                                                                                                  .... nullFlavor 0..1??Binding: ?? (required)0..1??Binding: ?? (required)
                                                                                                    .... realmCode 0..*CS0..*CS
                                                                                                      .... typeId 0..1IIC0..1II
                                                                                                      • StructureDefinition NotesSection has added constraint that is not found in NotesSection and it is uncertain whether they are compatible (root.exists() or nullFlavor.exists())
                                                                                                      ..... 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
                                                                                                              ..... extension 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
                                                                                                                .... templateId 0..*II0..*II
                                                                                                                  .... typeCode 0..1??Fixed Value: COMP0..1??Fixed Value: COMP
                                                                                                                    .... contextConductionInd 0..1??Fixed Value: true0..1??Fixed Value: true
                                                                                                                      .... section 1..1Section1..1Section

                                                                                                                        doco Documentation for this format