EMIS Web Adapter for QuickFHIR
2.0.0 - draft
EMIS Web Adapter for QuickFHIR
2.0.0 - draft
Publish Box goes here
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 EMIS Web 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.
| Bundle patient |
Who the data are about |
|||
| clinical-status |
|
|||
| clinical-status |
The clinical status of the condition |
|||
| status |
Immunization event status |
|||
| authoredon |
Return prescriptions written on this date |
|||
| identifier |
A patient identifier |
|||
| code |
Multiple Resources:
|
|||
| date |
Multiple Resources:
|
|||
| patient |
Multiple Resources:
|
|||
| birthdate |
Multiple Resources:
|
|||
| family |
Multiple Resources:
|
|||
| given |
Multiple Resources:
|
|||
| status |
Multiple Resources:
|
These define constraints on FHIR resources for systems conforming to this implementation guide.
| AdapterDefinition |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| EMIS Open Allergy Type Extension |
Extension for Allergy Types. |
| EMIS Open Consultation Header Element Extension |
Extension for EMIS Open Consultation Header. |
| Black Pear Observation Group Extension |
Extension for Observation Group. |
| Black Pear Observation Note Extension |
Extension for Observation Note. |
| EMIS Open Problem Status Extension |
Extension for Problem Status. |
| Registration Information Extension |
Registration Details for Patient. |
| Black Pear Repeat Prescriptions Extension |
Prescription repeat information for patient |
These define sets of codes used by systems conforming to this implementation guide.
| Allergy Type |
EMIS Open Allergy Type |
| EMIS Both |
Codes taken from the EMISBoth Code System. |
| EMIS Drug Constituent |
Codes taken from the EmisDrugConstituent Code System. |
| EMIS Drug Group |
Codes taken from the EmisDrugGroup Code System. |
| EMIS Drug Name |
Codes taken from the EmisDrugName Code System. |
| EMIS Preparation |
Codes taken from the EMISPreparation Code System. |
| Patient Type |
EMIS Open Patient Type |
| EMIS Problem Significance |
Codes taken from the ProblemSignificance Code System. |
| Problem Status |
EMIS Open Problem Status |
| Registration Status |
EMIS Open Registration Status |
These define new code systems used by systems conforming to this implementation guide.
| Allergy Type Code System |
EMIS Open Allergy Type Code System |
| EMIS Both Code System |
Allergy code from the appropriate code list restricted to EMISBOTH |
| EMIS Drug Constituent Code System |
Allergy code from the appropriate code list restricted to EMISConstituent |
| EMIS Drug Group Code System |
Allergy code from the appropriate code list restricted to EMISDrugGroup |
| EMIS Drug Name Code System |
Allergy code from the appropriate code list restricted to EMISDrugName |
| EMIS Preparation Code System |
EMIS User Dictionary Code System. These codes are bespoke and can change regularly |
| Patient Type Code System |
EMIS Open Patient Type Code System |
| EMIS Problem Significance Code System |
EMIS Significance Code System. |
| Problem Status Code System |
EMIS Open Problem Status Code System |
| Patient Registration Status Code System |
EMIS Open Patient Registration Status Code System |
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 EMIS Web 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 EMIS Web with a new encounter containing a document attachment. |