Announcement

Collapse
No announcement yet.

Mirth Connect adding "cda:" to XML elements

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

  • Mirth Connect adding "cda:" to XML elements

    I have a channel that removes certain information from segments and replaces it with randomized information. The channel works on CCDA documents from a one organization but with another it will add "cda:" to the XML headers. So while the incoming message might say
    Code:
    <streetAddressLine>123 Main St</streetAddressLine>
    The encoded message has the segment as:
    Code:
    <cda:streetAddressLine>1400 Johnson St</cda:streetAddressLine>
    Does anyone have any idea why this might be happening to some messages and not others? The addr structure is exactly the same between the 2 documents. Here is the code I am using to alter the streetAddressLine segment:

    Code:
    tmp['recordTarget']['patientRole']['addr'][0]['streetAddressLine'] = "1400 Johnson St";

  • #2
    namespace?

    Comment


    • #3
      Originally posted by mcalKno View Post
      namespace?
      I am not stripping namespace on the channel.

      Comment


      • #4
        Originally posted by craig.burdulis View Post
        I am not stripping namespace on the channel.
        Have an example of each (w/o PHI)?

        Comment


        • #5
          So I partially figured out the issue. If I change the ClinicalDocument header from:
          Code:
          <ClinicalDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:hl7-org:v3" xmlns:cda="urn:hl7-org:v3" xmlns:sdtc="urn:hl7-org:sdtc">
          to:
          Code:
          <ClinicalDocument xmlns="urn:hl7-org:v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          it is processed successfully and the encoded message does not have the "cda:" within the segment headers we changed. Any ideas on why that change made the difference?

          Comment

          Working...
          X