Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

In development

AllergyIntolerance (coming soon)

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

...

condition

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

...

medicationstatement

In development

AllergyIntolerance (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-conditionallergyintolerance

...

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

...

Consent (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-medicationstatementconsent

Organization (coming soon)

...