Page Comparison

...

Available Message Parsers

• ORUR01Handler: Built into core
  • Does not support the entire r01 specification
  • See below for example messages
  • Used by the FormEntry Module to process Infopath forms and xforms (HTML Form Entry is not using HL7)
• ADTA28: Built into core
  • (Link to page describing what is implemented)
• (Link to other parsers developed by the community??)

...

Different options to get into that import process:

1. Use the REST Module and its HL7 resource to post a message using curl or some other web service client.
2. Posting an HL7 message to url /remotecommunication/postHl7.form will insert the message into the hl7 in queue.
   • username: username to authenticate and save the message with
   • password: password to authenticate and save the message with
   • source: Name of an HL7Source in the system (A "LOCAL" hl7 source is shipped by default with openmrs)
   • hl7Message: The hl7 message to save
   • (Note: This was broken in 1.5.0, fixed against in 1.5.1 and 1.6+)
3. Using the API, a message can be parsed with Context.getHL7Service().parseHL7String(String) --> processHL7Message(Message);

...

• MSH|
  Message type (message header) and next character is the field separator

• 
  

  No Format
  ^~\&

  Encoding characters
  ^ ? component separator
  ~ ? repetition separator
  \ ? escape character
  & ? subcomponent separator

...

PV1 (Patient Visit) Key:

...