Suggest keeping DocumentReference profiles separate - USCore #88

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Core (FHIR)
    • STU3
    • Structured Documents
    • Profiles and Extensions
    • Hide

      Will merge and add Category, Author, and Custodian as Must Support. Will make clear how this supports clinical notes

      Show
      Will merge and add Category, Author, and Custodian as Must Support. Will make clear how this supports clinical notes
    • Eric Haas/Calvin Beebe: 23-0-6
    • Clarification

      Existing Wording: New DocumentReference and DiagnosticReport Profiles are being introduced for exchanging Clinical Notes. These are in addition to the existing US Core DocumentReference and US Core DiagnosticReport Profiles. Comments are requested on the question of whether these profiles and their use cases should be merged into a single DocumentReference and DiagnosticReport Profile.

      Comment:

      Seems these clinical-notes should be independent profiles that build upon the US-Core general versions of the profiles. The clinical-note is a targeted use-case. The results of that targeted use-case is a few further constraints. Thus the clinical-notes profiles would be compliant with the more general profiles.

      Summary:

      Suggest keeping DocumentReference profiles separate

            Assignee:
            Unassigned
            Reporter:
            John Moehrke
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: