🔗 Source article (Salesforce): Click here
The HL7 manual for users and internal IT. A description is given of possible scenarios in case the HL7 connection cannot be established.
General
The patient stands at the hospital reception and the eID card is read by the facturation clinic software. The facturation clinic software sends an HL7 message (TCP) to the HealthConvEx (Diabscan) server.
Example of the HL7 message:
URL: https://diabscan.win.local/api/v1/basicsecured/integrations/hl7
METHOD: POST
[HEADERS]
Authorization: Basic SEw3Ok5PRzZZTTk1RHBaUWNIQ0czeEFxRGhQaENmUWx5ajJLYXZzUnJwdjA=
Content-Type: x-application/hl7-v2+er7; charset=utf-8
[PARAMETERS]
[CONTENT]
MSH|^~\&|GIPS||||20180718122529||ADT^A01|55213525|P|2.3|||AL
EVN|A01||201807181226
PID|||305396|38381909|VVVVVVDDDDOLl^Jane||19810405|F|||Diabscanlaan 2 /B000^^Vilvoorde^^9999^Belgie||+32468152201||||||00040509826||||||||||""|N
PD1||||CCCCCCL^CCCCCCs^Ilse
PV1||O|EX^^||||LLLL^LLLLLLLs^Jan|LLLL^LLLLLLLs^Jan|CCCCCCL^CCCCCCs^Ilse|EX|||||||LLLL^LLLLLLLs^Jan||38381909|||||||||||||||||||||||||20180718122600|
IN1|1|2|322|DE VOORZORG||||||||||||VVVVVVDDDDOLl^Jane|0|||||||||||||||||||00040509826
ZIN||2|81040509826|110|11
Checklist
The following must be verified:
The URL for HealthConvEx (Diabscan) HTTPS or HTTP.
[HEADERS] validation with the diabscan token: If my token is = Bh7TI00Qa78QbYk76AFtJdDfttrd7rNbXi7TqIcx (see GUI HealthConvEx application under configuration). HL7 token = Bh7TI00Qa78QbYk76AFtJdDfttrd7rNbXi7TqIcx encoded in Base64 gives aGw3OkJoN1RJMDBRYTc4UWJZazc2QUZ0SmREZnR0cmQ3ck5iWGk3VHFJY3g= Thus my paragraph [HEADERS] must be like this: Authorization: Basic aGw3OkJoN1RJMDBRYTc4UWJZazc2QUZ0SmREZnR0cmQ3ck5iWGk3VHFJY3g=
Format date must be written with format date: yyyyMMdd.
Healthconvex-hl7.log file need to be verified for further details.
Scenario's
Error unable to find valid certification path to requested target from the Mirth server. HL7 messages are blocked and are no longer sent to the HealthConvEx (Diabscan) server correctly.
This means that MIRTH doesn’t trust the certificate of the HL7 API. The certificate used in the SSL connection is not trusted by the client. More info about this here.
No HL7 messages were sent correctly to HealthConvEx (Diabscan) because the SSL connection is not usable. Verify that the keystore (PFX file) that Mirth uses is still valid and contains an internal CA root certificate.
Error Unsupported Media Type
The header should contain "Content-type: x-application/hl7-v2+er7".
Technical documentation
This can also be found as a PDF under Files (scroll down the page).