@mayfield.g.kev I just spoke about the Keystone messaging interface because from my initial research it seems to be the easiest way to interact with EMIS, but maybe I am wrong (my knowledge on these subjects is minimal - GP system and NHS interoperability system in general).
From your comment I can assume that it will be possible to use DTS\MESH to delivery the messages to EMIS. If so, can you give me some more information about it?
Can I also have your comment about what I am tying to achieve with my poco and if my assumptions are the best way to implement it.
So, lets assume the following simple scenario:
Use Case: Send a message with clinical data (a few clinical codes and their values) to the GP system in order to allow the GP user to add “automatically” the information to the patient record.
Message: Because I know that the digital reporting of pathology test results are very common and that kind of messages can be used to communicate the data I need to send (health checks data). My ideia is to use this kind of messages, technically I am looking to the following messages:
HL7 v2 :: ADT - A31 (Update Patient Information) – Observation/Result
FHIR :: Observation and DiagnosticReport resources
Transport: Use MESH to delivery the messages
GP Systems: Process the messages in the following GP systems:
Vision :: via Mail Manager module (according to their documentation: "Health Check data received via the
pathology message route can now be filed into the patient record in the usual way using the Read codes received" )
EMIS Web :: via Keystone (this needs more investigation )
SystmOne TPP :: TBD (but maybe using the same approach used to process the pathology messages)
I’ve been struggling to find documentation regarding how the GP systems are consuming pathology messages or other DTS\MESH messages in general.
Can I have your opinion\comments regarding the assumptions\decisions above?