Stream: implementers
Topic: Composition type versus class
Katarina (Jun 27 2019 at 11:18):
What is the difference between Composition.type and Composition.class?
Eric Haas (Jun 27 2019 at 16:40):
in R4 is type and category but the question still remains...
Lloyd McKenzie (Jun 27 2019 at 20:22):
@Lisa Nelson ?
René Spronk (Jun 28 2019 at 15:38):
Probably same concepts as in IHE XDS - class/category being a coarse grained classification of the document type (20-50 concepts in the value set, e.g. "Imaging diagnostics"), and document type being a fine grained classification from (mostly) LOINC, e.g. "Nursing discharge summarization note". The example value set http://build.fhir.org/valueset-document-classcodes.html supports this, even if the wording doesn't.
Ken Sinn (Jun 28 2019 at 20:27):
If you look at the FHIR STU3 example bindings for Composition.class vs Composition.type, Composition.class are LOINC parts (http://hl7.org/fhir/STU3/valueset-doc-classcodes.html), while Composition.type are LOINC document types. In the move from STU3 to R4, the http://hl7.org/fhir/STU3/valueset-doc-classcodes.html set changed to http://hl7.org/fhir/valueset-document-classcodes.html, which is a bit confusing. See relevant discussion here: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Composition.2Eclass.2Fcategory.20example.20binding.20change.20in.20R4
Last updated: Apr 12 2022 at 19:14 UTC
