Hi Matt,

You'll find the full specification for HL7 over HTTP here:
http://hl7api.sourceforge.net/hapi-hl7overhttp/specification.html

1) what should the content type be for the response messages ER7
formatted hl7 requests (I'm thinking text/plain)

application/hl7-v2

(although as a part of preparation for balloting at HL7 this has been
changed to "application/hl7-v2+er7". HAPI currently won't accept the
latter, but the next version will accept either.)

2) Using the following code, how would I serialize the response message
for the http response stream?

Here is a complete example of sending a message using HAPI's HL7 over HTTP
implementation: http://hl7api.sourceforge.net/hapi-hl7overhttp/doc_hapi.html

3) are signers required?
4) Does anyone have an example of how signers are contstructed/implemented?

Depends what you mean by signers. There was a "signature header" present in
a previous version of the specification, but that was removed about a year
ago. I doubt it ever got used anywhere.

5) are there any headers that would be expected in Hl7 over http responses ?

Other than Content-Type (including charset=utf-8), no.

Cheers,
James


On Thu, Jun 5, 2014 at 3:49 PM, Matt Young <matt.yo...@payspan.com> wrote:

> I have some questions about hl7 over http.
> 1) what should the content type be for the response messages ER7
> formatted hl7 requests (I'm thinking text/plain)
> 2) Using the following code, how would I serialize the response message
> for the http response stream?
>   Parser p = hapiContext.getGenericParser();
>   Message resp= null;
>   Message hapiMsg;
>
>                         // The parse method performs the actual parsing
>   hapiMsg = p.parse(hl7Text);
>   respMsg= mainProcessor.processMessage(hapiMsg, new
> HashMap<String,Object>()); // mainProcessor implements
> ca.uhn.hl7v2.protocol.ReceivingApplication
>   // I don't know if the following would be right
> httpServletResponse.getOutputStream().write(respMsg.encode().getBytes());
> // what happens if the hl7Text contained xml?  what if it was ER7?
> 3) are signers required?
> 4) Does anyone have an example of how signers are contstructed/implemented?
> 5) are there any headers that would be expected in Hl7 over http responses
> ?
>
> The PaySpan e-mail gateway <mailgw01> made the following annotations.
>
> ------------------------------------------------------------------------------
> Confidentiality statement
> ***********************************************************************
> Notice: This e-mail message, including any attachments, is for the sole
> use of the intended recipient(s) and may contain confidential and
> privileged information.  Any unauthorized review, copy, use, disclosure,
> or distribution is prohibited.  If you are not the intended recipient,
> or not an agent of the intended recipient responsible for delivering this
> message, please contact the sender by reply e-mail and destroy all copies
> of the original message.[TW] 06/05/14, 15:49:59
>
>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Hl7api-devel mailing list
> Hl7api-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel

Reply via email to