Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-44682

Account.relatedAccount is problematic

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Account

    Description

      It's an anti-pattern to have a "typed" relationship unless there are a very large number of relationship types.  It makes assessing the 80% harder and requires slicing to set expectations.

      Also, in this case, the set of type codes is completely up in the air, so there's no basis for anyone understanding any of the relationships.  At minimum, it should be an extensible binding so there's at least a common understanding of key relationships.  (Note that additional relationships might be better handled using extensions anyhow.)

      Finally, the two codes that do exist don't seem to be mutually exclusive.  What's the expected behavior if they both hold?

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: