Capabilities: Aggregated Endpoint

Owned by Andrew Turner (Unlicensed)
Last updated: Dec 16, 2024 by Daniel Whiteley
8 min read

http://fhir.patientsknowbest.com/capabilitystatement/aggregated

https://www.hl7.org/fhir/R4/capabilitystatement.html

Released

AllergyIntolerance

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile for this resource type because data not originally provided in FHIR format is not currently mapped to FHIR.

Appointment

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-appointment

Condition

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-condition

Device

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

DeviceRequest

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

DeviceUseStatement

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

DiagnosticReport

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

DocumentReference

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Encounter

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile for this resource type because data not originally provided in FHIR format is not currently mapped to FHIR.

EpisodeOfCare

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Flag

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Immunization

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

ImmunizationRecommendation

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Medication

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

MedicationDispense

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

MedicationRequest

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB; non-FHIR medication data is migrated into a MedicationStatement instead.

MedicationStatement

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-medicationstatement

NutritionOrder

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Observation

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile for this resource type because data not originally provided in FHIR format is not currently mapped to FHIR.

Procedure

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Specimen

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

In development

These resource types can be sent to PKB, and will aggregate successfully, but cannot currently be extracted via the aggregation endpoint.

CodeSystem (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-codesystem

Consent (coming soon)

Profile:

The PKB aggregator does not aggregate Consent resources sent into customer upstreams.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-consent

Organization (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-organization

Patient (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-patient

Person (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-person

Practitioner (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-practitioner

PractitionerRole (coming soon)

Profile:

The PKB aggregator does not aggregate PractitionerRole resources sent into customer upstreams.

Resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-practitionerrole

ProcedureRequest (coming soon)

See ServiceRequest.

ServiceRequest (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

There is no PKB profile because this resource type is not generated by PKB.

Note that this resource type is R4 exclusive, and will contain resources mapped from the STU3 equivalent of ProcedureRequest.

ValueSet (coming soon)

Profile:

The PKB aggregator will include data from some upstream systems that do not have any profile validation on them (for example, Customer FHIR endpoints). As such, there is no base profile that can be relied upon other than the core FHIR definition.

However, resources returned from the Aggregated FHIR endpoint which represent data not originally provided in FHIR format will be mapped by PKB according to the following profile:

http://fhir.patientsknowbest.com/structuredefinition/aggregated-valueset