Capabilities: Aggregated Endpoint

Owned by Andrew Turner (Unlicensed)
Last updated: Jul 17, 2024 by Daniel Whiteley
4 min read

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

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

rest

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

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.

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.

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

In development

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

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-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 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-practitionerrole

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