Announcement

Collapse

NextGen (Mirth) Connect 3.10.0 Released!

NextGen (Mirth) Connect 3.10.0 is now available as an appliance update and on our GitHub page. This release includes better SQL Server database support, security improvements through fixes and library updates, and improvements for the Advanced Clustering plugin with a focus on improving performance of many of the tasks that are carried out on a frequent interval. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

please make the xml stay in incoming msg

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • please make the xml stay in incoming msg

    I would like to know how to why my xml on the incoming message always return to empty tags like this:

    <?xml version="1.0" encoding="UTF-8"?>
    <result/>

    Do I really need to paste each time??

    <?xml version="1.0" encoding="UTF-8"?>
    <result>
    <roomno>335</roomno>
    <medicalrecord_no>715</medicalrecord_no>
    <checkoutby/>
    <updatedby/>
    <patient_type>INDIVIDUAL-INPATIENT</patient_type>
    <remarks/>
    <packageid/>
    <roomtype>DL1P</roomtype>
    <admitted_date/>
    <updated_date/>
    <discharge>YES</discharge>
    <checkout>YES</checkout>
    <admissiondate>03-DEC-02</admissiondate>
    <admittedby/>
    <patient_no>2</patient_no>
    <attending_physician>JLO</attending_physician>
    <checkout_date>03-DEC-02</checkout_date>
    <dischargeby/>
    <roomcharge_date>2004-07-16</roomcharge_date>
    <discharge_date>03-DEC-02</discharge_date>
    </result>

    thanks guys!
    Tonet

  • #2
    Release make the xml stay in incoming msg

    Change your select statement to not do SELECT * but the actual fields. If you don't change the select statement though, Mirth shouldn't over-write the XML that is there.
    Chris Lang

    Comment


    • #3
      Release make the xml stay in incoming msg

      HI Chris!
      The actual fields are real many, and they are from various tables here without realtionships because I am working on a turnover system. Anyway, thanks for clearing it out to me!
      BY the way, union doesn't work here right? There is no other way for me to select all the required fields to populate my hl7 because inner join only works for referenced tables.
      Tonet

      Comment

      Working...
      X