TMS Implementation

Contents

1    Application Roles

The applications involved in the General Practice Extraction Service processes play specific roles.  These, along with the interactions associated with each role, are identified below.

1.1    GPET-Q System - COMT_AR000001GB01

The GPET-Q system is responsible for sending the following General Practice Extraction Service interactions:
GPET-Q-E Notification
GPET-Q-E Run-Time-Parameter Request
The GPET-Q System receives responses to the above interactions from the GPET-E System.
The GPET-Q system is responsible for receiving the following General Practice Extraction Service interactions:
GPET-E-Q Notification
GPET-E-Q Run-Time-Parameter Response
The GPET-Q System responds to the interactions from the GPET-E System.

1.2    GPET-E System - COMT_AR000002GB01

The GPET-E system is responsible for sending the following General Practice Extraction Service interactions:
GPET-E-Q Notification
GPET-E-Q Run-Time-Parameter Response
The GPET-E System receives responses to the above interactions from the GPET-Q System.
The GPET-E system is responsible for receiving the following General Practice Extraction Service interactions:
GPET-Q-E Notification
GPET-Q-E Run-Time-Parameter Request
The GPET-E System responds to the interactions from the GPET-Q System.

2    Trigger Events

2.1    GPET-Q-E Stage 1 Notification - COMT_TE000001GB01

The GPET-Q-E Stage 1 Notification trigger event indicates that a notification message requesting for the confirmation of participation in future scheduled query events is ready to send from the GPET-Q system.

2.2    GPET-Q-E Stage 2 Notification - COMT_TE000002GB01

The GPET-Q-E Stage 2 Notification trigger event indicates that a request for confirmation that query results sent from GPET-E-to GPET-Q can be sent to the GPES customer is ready to send from the GPET-Q system.

2.3    GPET-Q-E System Ping Notification - COMT_TE000003GB01

The GPET-Q-E System Ping Notification trigger event indicates that a request for the GPET-E System to provide system information is ready to send from the GPET-Q system.

2.4    GPET-E-Q Notification Response - COMT_TE000004GB01

The GPET-E-Q-Notification Response trigger event indicates that a response to the GPET-Q notification messages is ready to send from the GPET-E system.

2.5    GPET-E-Q Ad Hoc Notification - COMT_TE000005GB01

The GPET-E-Q Ad Hoc Notification Response trigger event indicates that an ad hoc notification of a system change/software upgrade/ processing errors is ready to send from the GPET-E system.

2.6    GPET-Q-E Runtime Parameter Request - COMT_TE000006GB01

The GPET-Q-E Runtime Parameter Request trigger event indicates that a GPES-Q-E-RTP message is ready to send from the GPET-Q system.

2.7    GPET-E-Q Receipt of Runtime Parameter Request - COMT_TE000007GB01

The GPET-E Receipt of Runtime Parameter Request trigger event indicates receipt of a GPES-Q-E-RTP message and that a GPES-E-Q-RTPR message is ready to send from the GPET-E system.

 

3    Interaction Diagrams

3.1    General Practice Extraction Service interactions

Note - Application Acknowledgements are sent to originating systems for notification of successful or failure handling by the receiving application.

 

4    Interactions

4.1    GPET-Q-E Run-Time-Parameter Request - COMT_IN000001GB01

Interaction Details
Interaction Name
Interaction ID
GPET-Q-E Run-Time-Parameter Request (Version 1.0) COMT_IN000001GB01
Interaction Description
Communicates a GPES-Q-E-RTP message to a GPET-E System where the recipient is recommended to act upon information carried in the message.
Sender Responsibilities
Trigger Message Name Message Definition
Sending of Message Message Type: GPES-Q-E-RTP (Version 1.0) COMT_MT000003GB01
Receiver Responsibilities
Trigger Response Name Response Definition
Receipt of Message Application Acknowledgment (Version 13.0) MCCI_IN010000UK13
  AND  
     
Receipt of Message GPES-E-Q-RTPR (Version 1.0) COMT_IN000002GB01
Transmission Details
Item
Name
ID
Transmission Wrapper Send Message Payload (Version 12.0) MCCI_MT010101UK12
Control Act Wrapper Control Act (Version 3.0) MCAI_MT040101UK03

4.2    GPET-E-Q Run-Time-Parameter Response - COMT_IN000002GB01

Interaction Details
Interaction Name
Interaction ID
GPET-E-Q Run-Time-Parameter Response (Version 1.0) COMT_IN000002GB01
Interaction Description
Communicates a GPES-E-Q-RTPR message to the GPET-Q System where the recipient is recommended to act upon information carried in the message.
Sender Responsibilities
Trigger Message Name Message Definition
Sending of Message Message Type: GPES-E-Q-RTPR (Version 1.0) COMT_MT000004GB01
Receiver Responsibilities
Trigger Response Name Response Definition
Receipt of Message Application Acknowledgment (Version 13.0) MCCI_IN010000UK13
Transmission Details
Item
Name
ID
Transmission Wrapper Send Message Payload (Version 12.0) MCCI_MT010101UK12
Control Act Wrapper Control Act (Version 3.0) MCAI_MT040101UK03

4.3    GPET-Q-E Notification - COMT_IN000003GB01

Interaction Details
Interaction Name
Interaction ID
GPET-Q-E Notification (Version 1.0) COMT_IN000003GB01
Interaction Description
Communicates a GPET-Q-E Notification message to a GPET-E System where the recipient is recommended to act upon information carried in the message.
Sender Responsibilities
Trigger Message Name Message Definition
Sending of Message Message Type: GPES-Q-E-NT (Version 1.0) COMT_MT000001GB01
Receiver Responsibilities
Trigger Response Name Response Definition
Receipt of Message Application Acknowledgment (Version 13.0) MCCI_IN010000UK13
  AND  
     
Receipt of Message GPES-E-Q-NT (Version 1.0) COMT_IN000004GB01
Transmission Details
Item
Name
ID
Transmission Wrapper Send Message Payload (Version 12.0) MCCI_MT010101UK12
Control Act Wrapper Control Act (Version 3.0) MCAI_MT040101UK03

4.4    GPET-E-Q Notification - COMT_IN000004GB01

Interaction Details
Interaction Name
Interaction ID
GPET-E-Q Notification (Version 1.0) COMT_IN000004GB01
Interaction Description
Communicates a GPET-E-Q Notification message to the GPET-Q System where the recipient is recommended to act upon information carried in the message.
Sender Responsibilities
Trigger Message Name Message Definition
Sending of Message Message Type: GPES-E-Q-NT (Version 1.0) COMT_MT000002GB01
Receiver Responsibilities
Trigger Response Name Response Definition
Receipt of Message Application Acknowledgment (Version 13.0) MCCI_IN010000UK13
Transmission Details
Item
Name
ID
Transmission Wrapper Send Message Payload (Version 12.0) MCCI_MT010101UK12
Control Act Wrapper Control Act (Version 3.0) MCAI_MT040101UK03

5    Message Definitions

        The message payload specifications are here

6    Message Examples Using TMS Wrappers

6.1    Examples for Scenario 1 (Scheduled Query on a single GPET-E system)

Examples for Spine Compliant Systems using scenario 1

 

Scenario 1 Artefacts
GPET-Q-E Notification example (COMT_IN000003GB01) interaction communicates a GPET-Q-E NT example (COMT_MT000001GB01) message to a GPET-E System. This is a Stage 1 data extraction notification sent to GPET-E. Payload Wrapped payload
GPET-E-Q Notification example (COMT_IN000004GB01) interaction communicates a GPET-E-Q NT example (COMT_MT000002GB01) message to the GPET-Q System. This is a Stage 1 notification response sent to GPET-Q.
GPET-Q-E Run-Time-Parameter Request example (COMT_IN000001GB01) interaction communicates a GPES-Q-E-RTP example (COMT_MT000003GB01) message to a GPET-E System. This is a Runtime Parameter request sent to GPET-E.
GPET-E-Q Run-Time-Parameter Response example(COMT_IN000002GB01) interaction communicates a GPES-E-Q-RTPR example (COMT_MT000004GB01) message to the GPET-Q System. This is a Runtime Parameter Response sent to GPET-Q.

6.2    Examples for Scenario 2 (System-Ping-Request-Notification to a single GPET-E system)

Examples for Spine Compliant Systems using scenario 2

 

Scenario 2 Artefacts
GPET-Q-E Notification example (COMT_IN000003GB01) interaction communicates a GPET-Q-E NT example (COMT_MT000001GB01) message to a GPET-E System. This is a system ping request notification sent to GPET-E to provide system information. Payload Wrapped payload
GPET-E-Q Notification example (COMT_IN000004GB01) interaction communicates a GPET-E-Q NT example (COMT_MT000002GB01) message to the GPET-Q System. This is the GPET-E '40000' event response to the system ping request.

6.3    Examples for Scenario 3 (Notification to GPET-Q of a system change)

Examples for Spine Compliant Systems using scenario 3

 

Scenario 3 Artefacts
GPET-E-Q Notification example (COMT_IN000004GB01) interaction communicates a GPET-E-Q NT example (COMT_MT000002GB01) message to the GPET-Q System. This is the GPET-E '40001' event notification of an initial installation of GPET-E Enabling Service Software. Payload Wrapped payload
GPET-E-Q Notification example (COMT_IN000004GB01) interaction communicates a GPET-E-Q NT example (COMT_MT000002GB01) message to the GPET-Q System. This is the GPET-E '40006' event notification.