TPP SystmOne Adapter for QuickFHIR
1.0.0 - draft
TPP SystmOne Adapter for QuickFHIR
1.0.0 - draft
TPP SystmOne Adapter for QuickFHIR - Local Development build (v1.0.0). See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Adapter capabilities |
Capabilities of the TPP SystmOne Adapter for QuickFHIR |
These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.
| authoredon |
Return prescriptions written on this date |
|||
| Bundle patient |
Who the data are about |
|||
| clinical-status |
|
|||
| clinical-status |
The clinical status of the condition |
|||
| code |
Multiple Resources:
|
|||
| date |
Multiple Resources:
|
|||
| family |
Multiple Resources:
|
|||
| given |
Multiple Resources:
|
|||
| identifier |
A patient identifier |
|||
| patient |
Multiple Resources:
|
|||
| status |
Immunization event status |
|||
| status |
Multiple Resources:
|
These define constraints on FHIR resources for systems conforming to this implementation guide.
| AdapterDefinition |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Adapter | |
| How to write a Condition |
Example of a Bundle resource used in create Bundle interaction. The adapter will update the record for patient 1714 within SystmOne with a new encounter containing a coded condition. |
| How to write a PDF document |
Example of a Bundle resource used in create Bundle interaction. The adapter will update the record for patient 1714 within SystmOne with a new encounter containing a document attachment. |