GP Connect - Update Record (ITK3)

Workflow

The term 'workflow' can be thought of as a work or task list.

Data from this specification must be ingested by the receiving system. A workflow task will always be generated. The practice can make a decision (as the controller) to auto-file this into the patient record or require that a Health or Care Professional (at the patient's GP practice) review the data before it is filed into the patient record.

Information must not be visible in Patient Facing Services functionality until reviewed by the Health or Care Professional at the Patient’s GP Practice.

Ingestion

The term 'ingestion' means that the healthcare data being sent via the transport mechanism (ITK3) is automatically understood by the receiver (GP system) and mapped to its internal data model.​

This is also commonly referred to as 'auto-ingestion'; however, it means the same thing.

Using someone’s name, as an example:​

If data isn't auto-ingested, then a person will have to manually copy and paste the incoming data into the supplier system in the patient record.

Historically, ITK3 has been used to transfer unstructured data, that is, HTML or PDF, which have been stored, and rendered as documents.

While this specification uses the same vehicle as those other specifications to transfer healthcare data, it does not allow HTML to be sent within the Composition.section.text element, and mandates that structured FHIR be sent in its place - in most cases, using the GP Connect Data model.​

Filing

The term 'filing' essentially means where the data is stored within the patient record within the supplier system. For example, the information relayed in the FHIR CareConnect-GPC-Encounter profile may sit within the Consultations section of a supplier system.

Auto-filing

The term 'auto-filing' relates to the automatic placement of information into the patient record, with no interaction from a human whatsoever.