| confidentiality code when submitting CDA works strangely [message #582987] |
Fri, 09 November 2007 20:34 |
 Jesse Pangburn
Messages: 166
Registered: July 2009 |
Senior Member |
|
|
Hi,
I've noticed odd (to me) behavior regarding the confidentiality code when
submitting a CDA document using the bridge. The submitDocument web
service method takes document Entry Confidentiality Code parameter, but at
least when you're submitting a CDA it seems to be ignored. I found this
while running test 11746 (simple doc submit) and getting an error back
from the repository that the confidentiality code was missing.
In the log there was no confidentiality code in the submission, but it was
logged as a parameter to the web service- so I believe I passed the
parameter correctly. When I then added a confidentiality code inside the
CDA document I was submitting, then that code got written into the
submission to the repository and it was happy. I added the code like this:
<confidentialityCode code="N" codeSystem="2.16.840.1.113883.5.25"
codeSystemName="Connect-a-thon confidentialityCodes" displayName="Normal"/>
I know that the bridge reads the CDA to determine a number of the meta
data fields that it submits to the repository, but it seems like a bug
that there is a parameter to the service for confidentiality code but it
just gets ignored. It could be a problem if the CDA has a confidentiality
code and so does the web service parameters and they are different, so I
suspect this is how this bug came about.
Perhaps the parameter to the web service should be ignored if there's one
in the CDA (or maybe it should override, I'm not sure), but if there's
none in the CDA then it seems that the web service parameter should
definitely be used.
thanks,
Jesse
P.S. Sorry for so many posts lately :-)
|
|
|
Powered by
FUDForum. Page generated in 0.03811 seconds
] 
Search
Help
Register
Login
Home
