|
Send Online Consultation Report to GP practice
|
As member of staff at a GP practice... I want the Online Consultation Report to be sent directly to the GP clinical system... so that I don't have to manually move or copy the Online Consultation Report.
|
Sending system
-
the sender system must send an Online Consultation Report to the patient's registered GP practice
-
the sender system must flag the Online Consultation Report as FOR ACTION if the GP practice is identified as the primary recipient
-
the send system must flag as FOR INFORMATION and send a copy message if an alternative care provider is identified as the primary recipient
-
where the sender system supports an alternative method for communicating the online consultation information back to the patient's registered GP practice, this method may be used in the place of GP Connect Messaging
-
where an alternative method is used, the GP Connect Messaging requirements do not apply
Receiving system
Not applicable
|
|
Send Online Consultation Report directly to an alternative care provider
|
As member of staff at a GP practice... I want the Online Consultation Report to be sent directly to an alternative care provider selected by the patient... so that the care provider can offer a service to the patient.
|
Sending system
-
the sender system must send an Online Consultation Report to the patient's chosen alternative care provider (currently only community pharmacies)
-
the sender system must flag the Online Consultation Report as FOR ACTION
-
a copy message must be sent to the patient's registered GP practice flagged as FOR INFORMATION
Receiving system
Not applicable
|
|
Routing the report to the correct care provider
|
As member of staff at a GP practice... I want the Online Consultation Report to be routed to the patient's registered practice or chosen alternative care provider... so that the message is sent to the correct destination(s).
|
Sending system
- all sending systems will use the MESH API Address Lookup function to request/receive the destination system's MESH mailbox IDs
-
when sending the Online Consultation Report
-
the sender system should use the MESH API Send Message function to send the message
-
the sender system can use the MESH client to send the message
- if the sender system is only ever sending the Online Consultation Report to the patient's registered GP practice, then MESH automated message routing function can be used
- the sender system must use the allocated MESH Workflow ID associated solely with this capability
Receiving system
- when sending to a GP practice, if the message received is for a patient who is not registered at the GP practice, the receiving system must send a response back to the sending system
- the receiving system must use the allocated MESH Workflow ID associated solely with the GP Connect Send Document capability
|
|
SNOMED coding applicable content
|
As clinician at a GP practice... I want the Online Consultation Reports to be SNOMED coded where applicable... so that I don't have to manually code clinically relevant information into the patient's record.
|
Sending system
-
the sender system must SNOMED code all clinically relevant information in an Online Consultation Report sent to the patient's practice
-
the sender system must use a SNOMED code for a defined collection of Clinical indicators
Receiving system
- the receiving system should have the ability to consume the additional structured data contained in the extended payload
- the receiving system should allow review and confirm before the SNOMED coded information is saved to the patient's record
|
|
Payload identification
|
As clinician at a GP practice... I want the Online Consultation Report, and its information, to be clearly identifiable... so that the provenance of the information is clear.
|
Sending system
- the sending system must contain a SNOMED coded OC identifier
- the sender system must identify items in the payload as patient entered information, where applicable
Receiving system
- the receiving system must display the OC identifier sent in the payload by the sender system
- the receiving system should be able to display items flagged as patient entered information
|
|
Non-coded payload content
|
As clinician at a GP practice... I want the ability to save all the non-coded information in the Online Consultation Report to the patient record... so that I can add all clinically relevant information to the patient record.
|
Sending system
- the sender system must include a PDF of the Online Consultation Report in the payload
- the sender system must be able to contain one or more images or supported attachment types
Receiving system
- the receiving system must be able to save the PDF in the Online Consultation Report to the patient record
- the receiving system must be able to save one or more attachments in the patient record
- where images are contained in the payload, the receiving system must record them in the audit trail
|
|
Triage
|
As clinician at a GP practice... I want the OC system to be able to triage the information in the Online Consultation AND send the OC payload either to the GP or an alternative care provider, dependent on the triage outcome... so that the patient receives the correct level of care.
|
Sending system
- the sender system should be able to auto triage based on the patient entered symptom information in an Online Consultation Report, AND make a routing decision (GP or alternative care provider)
- the sender system should be able to send the OC payload to a GP or alternative care provider, if there is manual triage functionality available within the OC system
Receiving system
NA
|
|
Patient preference of alternative care provider
|
As clinician at a GP practice... I want a patient to be able to give a preference of an alternative care provider (for example, community pharmacy) in their locality whenever they complete an Online Consultation Report... so that the Online Consultation Report can be directed to a preferred alternative care provider.
|
Sending system
- the sender system must offer the patient a list of local alternative care providers (for example, Community Pharmacies) AND record the patient's entered preference
- the sender system must include the patient's response for the alternative care provider preference in the Online Consultation payload
Receiving system
NA
|
|
Send Online Consultation Report from an alternative care provider back to a GP
|
As a member of staff at an alternative care provider... I want to be able to send the Online Consultation Report back to the GP system... so that escalated Online Consultation Reports can be returned to the patient's registered GP practice for further action.
|
Sending system
- the sender (alternative care provider) system must be able to send the OC payload back to a GP system if required
Receiving system
- the receiving system (GP system) must be able to receive an Online Consultation Report sent from an alternative care provider if escalated
|