Tweet
Hello,
I'm working on a project which aims at adding to medical devices the ability to connect to HIS to retrieve
informations like Patient ID or specific patient data (e.g weight)
In order to validate these new functionalities, we consider the following strategy:
1) at unit level: check that we are able to generate valid HL7 requests.
2) a validation level, check that the HIS can manage the requests our application may send.
I think I can use Mirth Connect for the 1st point: say we want to send a HL7 request consisting in
a ITI-21 IHE FindCandidate request (aka QBP^Q22 query). I'd like to use Mirth Connect to verify that the request is correct wrt
its definition (type/multiplicity of parameters, contents of certain fields of segment, etc.)
I already succeeded in receiving a HL7 message (sent by another tool)
and sending back an ACK or NACK depending on the value of a given field.
My concern is to limit the source code to be written so that I reduce the risk of writing a "bad" validator which
would accept a badly-formed request.
I'm quite sure I am not the first to face this problem so how do you guys, solve it ?
Vincent
I'm working on a project which aims at adding to medical devices the ability to connect to HIS to retrieve
informations like Patient ID or specific patient data (e.g weight)
In order to validate these new functionalities, we consider the following strategy:
1) at unit level: check that we are able to generate valid HL7 requests.
2) a validation level, check that the HIS can manage the requests our application may send.
I think I can use Mirth Connect for the 1st point: say we want to send a HL7 request consisting in
a ITI-21 IHE FindCandidate request (aka QBP^Q22 query). I'd like to use Mirth Connect to verify that the request is correct wrt
its definition (type/multiplicity of parameters, contents of certain fields of segment, etc.)
I already succeeded in receiving a HL7 message (sent by another tool)
and sending back an ACK or NACK depending on the value of a given field.
My concern is to limit the source code to be written so that I reduce the risk of writing a "bad" validator which
would accept a badly-formed request.
I'm quite sure I am not the first to face this problem so how do you guys, solve it ?
Vincent