fhir messaging - Rene Spronk
-
Upload
devdays -
Category
Healthcare
-
view
537 -
download
0
Transcript of fhir messaging - Rene Spronk
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Messaging
FHIR Messaging
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Messaging
Loosely coupled Destination may not be available Store and forward architecture Worst case assumption – send rich set of data
each and every time, receiver to select/process relevant parts
Trigger event based Trigger Event = Business reason for data
exchange, sets expectations as to response
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.3
Basic Principles of HL7 Messaging
sendHL7 message
receive HL7 ACK message
Receive HL7 message
send HL7 ACK message
Triggerevent
System A System B
network
Could be any transport: tcp/ip, RS232, Webservices, REST, etc.
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.4
Message Exchange Mechanisms
Server
(Data Owner)
Client
(InterestedParty)INTERROGATIVE
Query
Response
DECLARATIVEEvent
ReceiptAcknowledgment
ApplicationAcknowledgement
IMPERATIVEOrder
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
5
Message Structure
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
6
Sync / Async messaging patterns
SyncBlocking wait
Message
Response Message
HTTP: request/response
Response Message
Message
HTTP: request/200
request/200
Async
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
7
REST: $process-message operation Operation accepts a message, returns
response message
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
8
Queries in messages
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
9
Operations in messages
Invoke a RESTful operation via messaging Same mechanism for query and operation
Trigger Event = Operation Name Operation outcome as a message
Same trigger event: Operation Name
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
10
Orders / workflow
Trigger Event has workflow aspects (“do this”)
RESTful paradigm will need special resources to manage workflow Otherwise, one is just recoding what ahs
happened already Intent is to re-use across all paradigms
As of yet unknown how this will impact messaging and the concept of ‘trigger event’
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
11
Summary
FHIR Messaging can support all of the ‘traditional’ messaging scenarios.
Loosely coupled scenarios. Same resources and workflow control as
RESTful paradigm or FHIR Documents.
HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
QUESTIONS?