Clarify how DocumentReference.type and DocumentReference.class differ

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Structured Documents
    • STU
    • DocumentReference
    • Hide

      Pursuasive with Mod

      Apply same change from 8057 to DocumentReference (and as applicable to DocumentManifest), with editoral as needed to change Composition to DocumentReference.

      Show
      Pursuasive with Mod Apply same change from 8057 to DocumentReference (and as applicable to DocumentManifest), with editoral as needed to change Composition to DocumentReference.
    • John Moehrke / Keith Boone: 4-0-0
    • Clarification
    • Non-substantive
    • DSTU1 [deprecated]

      The documentation for type says:

      Specifies the particular kind of document.

      Whereas class says:

      A categorization for the type of document.

      One of these fields has example values of "Patient Summary" and "Prescription", whereas the other has example values of "Patient Preferences" and "Summary". I don't know what principles a reader is supposed to discern from reading these descriptions and examples; the distinction is unclear.

      If possible these fields should be collapsed. If they are both needed, then further work is required to clarify why.

            Assignee:
            Unassigned
            Reporter:
            Josh Mandel
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: