Page Comparison

...

Resource types sent to a Customer FHIR endpoint which are to form part of the patient’s record always have some way of referring to the patient (e.g. Condition.subject, Appointment.participant). The Customer can optionally declare the source of such data by ensuring the target Patient resource uses Patient.managingOrganization to refer to an Organization which represents the source of the data. Optionally, PKB can configure a default Organization to be used when the source is not provided explicitly. The PKB web interface will display the name of this Organization as the “source”. Note that in this way a single Customer can provide data from multiple Organizations on the same endpoint.

• If no managingOrganization is present, the PKB web interface will not display any source informationwill use the default Organization. It is an error for there to be no managingOrganization on an integration with no default Organization configured; every resource sent to a Customer endpoint must have a source Organization.

• The details of the managingOrganization are controlled by the Customer; this information is not authenticated by PKB.

• The managingOrganization is not populated on a Patient returned from the Aggregated FHIR endpoint, because Patient is a resource type that is merged and source-tracking on merged resource types is handled differently (see below).

meta.security contains a code codes that indicates the resource ID of the relevant source entities. For data sent to a Customer FHIR endpoint, this code represents . Customers should not set these values themselves; PKB will ensure the codes are set correctly. These codes are an implementation optimisation, e.g. removing the need for a caller to fetch the chained managingOrganization. For data migrated from a non-FHIR input route, the migration process will ensure this code is populated correctly. Note that these codes are not populated for resource types that are merged, because source-tracking on merged resource types is handled differently (see below). The possible code systems are:

• source-organization (note that this refers to a FHIR Organization resource which may or may not correspond to a PKB Organisation)

• source-patient

• source-practitioner

• source-team

Note that these codes are not populated for resource types that are merged, because source-tracking on merged resource types is handled differently (see below).

The http://fhir.patientsknowbest.com/structuredefinition/upstream extension adds an additional level of source tracking, by tracking which of the upstream endpoints the information returned by the Aggregated FHIR endpoint actually came from.

...