web stats
Mirth Connect adding "cda:" to XML elements - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 02-04-2016, 06:30 AM
craig.burdulis craig.burdulis is offline
Mirth Newb
 
Join Date: Jan 2016
Posts: 7
craig.burdulis is on a distinguished road
Default 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";
Reply With Quote
  #2  
Old 02-04-2016, 06:47 AM
mcalKno mcalKno is offline
 
Join Date: Apr 2015
Location: Pennsylvania
Posts: 247
mcalKno is on a distinguished road
Default

namespace?
Reply With Quote
  #3  
Old 02-04-2016, 08:19 AM
craig.burdulis craig.burdulis is offline
Mirth Newb
 
Join Date: Jan 2016
Posts: 7
craig.burdulis is on a distinguished road
Default

Quote:
Originally Posted by mcalKno View Post
namespace?
I am not stripping namespace on the channel.
Reply With Quote
  #4  
Old 02-04-2016, 08:36 AM
mcalKno mcalKno is offline
 
Join Date: Apr 2015
Location: Pennsylvania
Posts: 247
mcalKno is on a distinguished road
Default

Quote:
Originally Posted by craig.burdulis View Post
I am not stripping namespace on the channel.
Have an example of each (w/o PHI)?
Reply With Quote
  #5  
Old 02-04-2016, 10:32 AM
craig.burdulis craig.burdulis is offline
Mirth Newb
 
Join Date: Jan 2016
Posts: 7
craig.burdulis is on a distinguished road
Default

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?
Reply With Quote
Reply

Tags
ccda, cda, connect, element, xml

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 07:40 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation