Consider having a pattern for Patient and similar resources

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Administration
    • Patient
    • Hide

      The following changes will be made to align the properties in the Patient, Practitioner, RelatedPerson and Person resources to be consistent with patient (and each other).

      Person - move active after identifier, and include identifier and address in the summary, change the photo to 0..*

      Practitioner - move telecom, birthDate, gender, and address into same order as patient

      Otherwise the naming and cardinalities of these properties are all the same. (However the summary fields are different)

      If additional resources are added that match this "pattern" we may consider creating a formal pattern, however PA does not expect that there will be new resources created, hence don't think that a formal pattern will provide any added value.

      Show
      The following changes will be made to align the properties in the Patient, Practitioner, RelatedPerson and Person resources to be consistent with patient (and each other). Person - move active after identifier, and include identifier and address in the summary, change the photo to 0..* Practitioner - move telecom, birthDate, gender, and address into same order as patient Otherwise the naming and cardinalities of these properties are all the same. (However the summary fields are different) If additional resources are added that match this "pattern" we may consider creating a formal pattern, however PA does not expect that there will be new resources created, hence don't think that a formal pattern will provide any added value.
    • Alexander Henket/Cooper Thompson: 8-0-0
    • Enhancement
    • Non-compatible

      We are currently using patterns to good effect to document "equivalencies" across resources and to help identify places where resources are not as consistent as they might be and confirming that variances are intended. The intention is to leverage these pattern mappings into constructs that can be supported within the reference implementations. It seems like there would be a benefit to having a pattern that covered Patient, RelatedPerson, Practitioner and possibly Person, Organization and/or Device. Or perhaps a couple of patterns. Given that we're looking at locking Patient down, it would be good to get these patterns in place and this analysis done prior to lockdown rather than after (though given that only Patient is being locked down, it does mean that all other resources can be aligned with Patient if it does get locked down first.)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: