Merging DocumentReference into single profile - USCore #181

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • Structured Documents
    • DocumentReference [deprecated]
    • Profiles and Extensions
    • Hide

      Will merge DocumentReference profile, and keep the DiagnosticReport separate. Will make clear the differences

      Show
      Will merge DocumentReference profile, and keep the DiagnosticReport separate. Will make clear the differences
    • Eric Haas/Calvin Beebe: 23-0-6
    • Clarification
    • Non-compatible

      Comment:

      As to merging the "new" with the existing, my question is about the meaning of a category code in the new specification. This code, as presented in the examples, seems unnecessary. If the two are not merged then the naming convention and explanation must be much more clear about the reason for having two profiles.

      Summary:

      Merging DocumentReference into single profile

            Assignee:
            Unassigned
            Reporter:
            rberge
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: