2015May core #163 - Why both type and class?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Structured Documents
    • Composition
    • Clarification

      Existing Wording: Composition.type: Type of a composition

      Composition.class: High-level kind of a clinical document at a macro level

      Proposed Wording: Composition.type: Type of a composition

      Comment:

      It is unclear in the current documentation the relationship and any rules which may apply when using class and type within compositions. It seems as if the valueset defined for class code is a subset of the codes that could be selected for type. Type is required, abd class is optional.

      Unless a rational is defined for the inclusion of class, it would seem redundant and best expressed as an extenstion.

      No rules for use and explaination as to why two document ontology references are required for Composition. Lacking a clear need, it would seem that class could be removed from the composition class.

            Assignee:
            Unassigned
            Reporter:
            Calvin E. Beebe
            Calvin E. Beebe
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: