Coverage profile restricts the .subscriber to a RelatedPerson

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Bidirectional Services eReferrals (BSeR) (FHIR)
    • STU3
    • Public Health
    • (profiles) [deprecated]
    • Hide

      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.

      Show
      Requirements traceability mappings and instance examples will be added to all profile defintions. Any existing gaps in fulfillment of identified requirements we be resolved during the process.
    • AMS/Mead: 14-0-0
    • Clarification
    • Non-substantive

      The BSeR Coverage profile seems to limit .suscriber to being a RelatedPerson resouce. What happens is the beneficiary is also the subscriber? Does there have to be a RelatedPerson resource linked to the Patient resource with a .relationship value of ONESELF? That seems overly complicated. Can .subscriber be changed to allow a reference to either a Patient or RelatedPerson?

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: