Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28354

Cardinality questions for CatalogHeader profile

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • Order Catalog (FHIR)
    • 0.1.0
    • Orders & Observations
    • Catalog Header Profile
    • Hide

      Motion to:

      1. Change Composition.type.text to 1..1 (per CI Build already pre-applied)
      2. Keep Composition.category to 0..* (per CI Build should go back to what it was in STU 1 ballot version) because this can be applied to more than one category. 

      Rationale to keep it 0..* as a 1..* would require a clearly defined value set, not just examples, that allow for clear ability to at least have one category at all times.

      Show
      Motion to: Change Composition.type.text to 1..1 (per CI Build already pre-applied) Keep Composition.category to 0..* (per CI Build should go back to what it was in STU 1 ballot version) because this can be applied to more than one category.  Rationale to keep it 0..* as a 1..* would require a clearly defined value set, not just examples, that allow for clear ability to at least have one category at all times.
    • Marti Velezis / JD Nolen: 6-0-1
    • Enhancement
    • Non-compatible

    Description

      Should Composition.type.text and Composition.category both be 1..1 to ensure they are both always populated? This would better match the base R4 catalog profile on Composition (http://hl7.org/fhir/R4/catalog.html)

      Attachments

        Activity

          People

            jdlnolen John D.L. Nolen
            craig.newman Craig Newman
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: