Use case for the MESH API

To use the MESH API you must have a valid use case.

Provide more details on the purpose of your product and describe the use case(s).

Help and tips for completing this section

You demonstrate that you have a valid use case to access MESH data by providing specific information.

The MESH team manage the process and will review and approve the information you provide.

Find out more about how to access data on the MESH API Service.

Q.1

Will your product be used for one of the defined use cases?

  • WL1: Management of patient screening (including results)
  • WL2: National data opt-out management
  • WL3: Sending of consultation/treatment information to a patient's GP (for example, in PDF format)
  • WL4: Sending documents to a patient's GP (for example, in PDF format)
  • WL5: Sending Transfer of care information between care providers (including GP)
  • WL6: Management of patient vaccinations information
  • WL7: Patient monitoring and surveillance activities (as part of health protection regulation)
  • WL8: GP registrations and change of GP events
  • WL9: Outcome of NHSE commissioned health improvement initiatives to a patient's GP
  • WL10: Sending of information for payment purposes
  • WL11: Transfer of social care Child Protection information
  • WL12: Management of patient test results
  • WL13: Sending remote (OC/VC) consultation information to a patient's GP
  • WL14: Management of child health information
  • WL15: Management of Discharge Summaries
  • WL16: Management of Shared Care Plans
  • WL17: Changes to PDS data
Q1.1

Which use case applies to your product?
Q.2
Supporting information

Where more than one organisation is involved, it is often useful to provide a Context Diagram with supporting narrative, providing an overview of the ‘player’ organisations, the data flows between them, and the types of users in each organisation.

If you have access to a business analyst that will help. We do not want wholly technical architecture diagrams. Where a Context Diagram is supplied, provide accompanying narrative, in plain English.

You can enter up to 2000 characters

Do you want to upload supporting files to describe the purpose and use case of your product?
You can upload one file that is smaller than 250MB. If you need to provide multiple files you should zip them up and upload them as a single .zip file.
Q.3

Have you considered the impact of rolling out the MESH Service on staff and job roles?

The use of the MESH Service could increase the work load of front-line staff.

Any implications and required additional training of this additional activity must be considered.

Piloting and a phased rollout would typically be used as part of this approach.
You can enter up to 2000 characters
Q.4

Will your product only be used for the use cases you have described?
You can enter up to 2000 characters
Back to MESH OCT 24