-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
Structured Documents
-
Composition
-
-
Calvin Beebe / Brett Marquard: 29-0-2
-
Clarification
-
Non-substantive
-
DSTU1 [deprecated]
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.
- is duplicated by
-
FHIR-7104 2015May core #163 - Why both type and class?
-
- Duplicate
-
- is voted on by
-
BALLOT-2033 Negative - Calvin E. Beebe : 2015-May-FHIR SDC R1
- Balloted