[FHIR Road Map] Practitioner Roles assignment enhancements

[dubdabasoduba]

@machariamuguku I reviewed the work and I think I missed something while scoping this.

We are also using the PractitionerRole resource while adding Practitioners to Teams (Organization). Could we just use the same PractitionerRole payload created during practitioner creation instead of creating a new one during team assessment?

Here is a sample of a PractitonerRole used for the team assignment. Notice the organization attribute

{
  "resourceType": "PractitionerRole",
  "id": "9",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2022-09-01T12:41:06.990+00:00",
    "source": "#12924984e2337d6b"
  },
  "identifier": [
    {
      "use": "official",
      "value": "b551632c-cfe8-4436-84ff-4947022ee47f"
    }
  ],
  "active": true,
  "practitioner": {
    "reference": "Practitioner/6",
    "display": "Brown  Bag"
  },
  "organization": {
    "reference": "Organization/8",
    "display": "Brown Bag"
  }
}

Can we have the team assignment behave as follows?

• Load the PractitionerRole resource tied to the Practitioner. This can be loaded using a search on the PractitionerRole resource filtered by practitioner.
• Update the PractitionerRole and add the organization attribute during the user assigned to the team.
• In case a user is un-assigned we then remove the organization attribute from the PractitionerRole.
  • This means the team assignment piece should not alter the active attribute.

Here is a sample of a PracttionerRole resource with both the team assignment and FHIR user role

{
  "resourceType": "PractitionerRole",
  "id": "",
  "identifier": [
    {
      "use": "official",
      "value": "auto-generated-d"
    },
    {
      "use": "secondary",
      "value": "keycloak-uuid"
    }
  ],
  "active": true,
  "practitioner": {
    "reference": "Practitioner/practitioner-id"
  },
  "code": [
    {
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "236321002",
          "display": "Supervisor (occupation)"
        }
      ]
    }
  ],
  "organization": {
    "reference": "Organization/8",
    "display": "Brown Bag"
  }
}

Originally posted by @dubdabasoduba in #1095 (comment)

[dubdabasoduba]

@machariamuguku how far are we with this?

[machariamuguku]

@machariamuguku how far are we with this?

@dubdabasoduba this is pending from last year. I'll prioritise this the beginning of this week

[dubdabasoduba]

Implementation updates

• In case the user does not have a PracttionerRole resource already created we would create a new PracttionerRole resource when adding them to a team.
  • We would then use the same PractitionerRole resource when adding a practitioner role Practitioner or Supervisor to them.
• When we remove someone from a team assignment. We would remove the organization attribute from the Practitioner Resource.

[machariamuguku]

@dubdabasoduba can a practitioner only be assigned to a single organisation?

[dubdabasoduba]

@dubdabasoduba can a practitioner only be assigned to a single organization?

For now, this is the restriction on OpenSRP. I think that's how we have built it. Let me review this with the PMs and then get back to you.

[machariamuguku]

I will also update the practitioner role created at practitioner creation to include the practitioner display name attribute for consistency

[machariamuguku]

@dubdabasoduba I identified an issue idk if it's by design: after modifying a practitioner role by either modifying the (adding or removing organisation attribute) or creating a new resource, the newly modified/created practitioner role is not immediately available on the practitioner role endpoint till 35-40 seconds later. Confirmed the same by hitting the server directly with postman

endpoint: https://ecbis-preview.smartregister.org/fhir/PractitionerRole/_search?organization=organization-id