Thanks for the exhaustive answer, as always. It's nice to hear that these
issues have already been addressed.
Good job!
On Mon, Feb 3, 2014 at 11:10 PM, James Agnew wrote:
> Hi Giacomo,
>
> Unfortunately this is a case of the code being behind the specification.
> At the previous HL7 working gr
Hi Giacomo,
Unfortunately this is a case of the code being behind the specification. At
the previous HL7 working group meeting the ITS (implementable technology
specification) group approved two changes to the spec:
* HTTP 200 response code for all valid HL7 message responses (the rationale
being
Hi, I think that there is a mismatch between the HL7 Over HTTP
specification and the current implementation regarding the HTTP Response
Codes.
The specification says:
When a *receiving application* produces an HL7 response payload containing
> one of these status codes (AR, AE, CR, CE), this is co
3 matches
Mail list logo
