Archives: <span>FAQs</span>

What is the Test Harness?

NHS Digital have developed a Test Harness with GP Synthetic Client and Hospital Synthetic Client capabilities. The Test Harness is hosted in the OpenTest environment and can operate as a GP Synthetic Client or Hospital Synthetic Client.   Secondary care organisations would send via MESH, messages to a GP synthetic client, which would send back responses as if from an enabled real GP IT system.

Read the full article...

Will the ORD code changes impact on ITK FHIR or MESH?

MESH is the transport layer and ITK provides the distribution envelope.   Organisations change their Org code, i.e. Organisation Data Service (ODS) code on a regular basis due to activities such as merges at Trust and General Practice level.  ODS provides important addressing or identifying information (such as security certification) for MESH and ITK.   The MESH End Point Lookup function can discover the MESH Mailbox ID by providing an ODS code.  

Read the full article...

Can CDA be used?

CDA has been deprecated for use within ToC to minimise the burden on supporting multiple send / receive types.  The previous levels are still valid and can be applied equally to FHIR.  The messages will contain the same components: meta data about the document, text of the document and coded entries.  The embedding of PDFs etc. as the document is not a valid implementation and as a minimum structured text is expected.  Structured, coded entries should also be included where possible.

Read the full article...

Does the generic FHIR ‘receive’ capability support a generic document structure in addition to ToC flows?

The proposed capability is for any type of message and will work by transferring documents into the GP workflow/system where the receiving system will manage receipt. Currently, there isn’t a generic document structure as focus has been on the four ToC types. These documents will have common FHIR resources but not follow a generic structure.

Read the full article...