Eclipse Community Forums: OHF » confidentiality code when submitting CDA works strangely

Help

Home

Home » Archived » OHF » confidentiality code when submitting CDA works strangely

Show: Today's Messages :: Show Polls :: Message Navigator

confidentiality code when submitting CDA works strangely [message #36830]

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 :-)

Report message to a moderator

Re: confidentiality code when submitting CDA works strangely [message #36864 is a reply to message #36830]

Sun, 11 November 2007 18:46

No real name

Messages: 292
Registered: July 2009

Senior Member

Hi Jesse,

You are on a roll :-) I think this is a problem that the bridge is not
overriding the confidentiality code as it should with the one provided
by the bridge user.

We do extract this information from the CDA ... however, metdata
extraction is imperfect for two reasons:
#1 XDS metadata for a submission cannot all be found in a CDA document
(scope problem).
#2 CDA requires different codes from different vocabularies than what
XDS metadata requires (termininology problem).

#2 is the problem that codes fall into ... so the bridge just overrides
these from user input rather than hooking ourselves up to some
terminology server or attempt sophisticated code mapping algorithms at
this time. We may try to be more sophisticated in the future.

So, in short, please submit another bug and I'll add it to our queue.
Please attach logs (especially where it shows the xds metadata as ebXML)
.... as I think this just a problem with the overriding that did not get
propegated to the bridge (but is in the underlying plugin).

Also, we are at a conferece this week (which is why i'm working on
Sunday). I'll attempt to attack your bug list ASAP, but just wanted to
let the community know that we will be delayed this week.

Regards,
- Sarah

Jesse Pangburn wrote:
> 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 :-)
>

Report message to a moderator

Re: confidentiality code when submitting CDA works strangely [message #36967 is a reply to message #36864]

Mon, 12 November 2007 17:22

Jesse Pangburn

Messages: 166
Registered: July 2009

Senior Member

Hi Sarah,
I noticed the Sunday working thing, I was thinking "wow, IBM's got some
serious slave drivers!" But a conference is understandable :-)

So, I created Bug 209527
https://bugs.eclipse.org/bugs/show_bug.cgi?id=209527 for this. This one's
easy enough for people to workaround for preliminary testing, just add the
confidentiality code in the CDA.

Thanks a bunch, enjoy your conference!
Jesse

Sarah Knoop wrote:

> Hi Jesse,

> You are on a roll :-) I think this is a problem that the bridge is not
> overriding the confidentiality code as it should with the one provided
> by the bridge user.

> We do extract this information from the CDA ... however, metdata
> extraction is imperfect for two reasons:
> #1 XDS metadata for a submission cannot all be found in a CDA document
> (scope problem).
> #2 CDA requires different codes from different vocabularies than what
> XDS metadata requires (termininology problem).

> #2 is the problem that codes fall into ... so the bridge just overrides
> these from user input rather than hooking ourselves up to some
> terminology server or attempt sophisticated code mapping algorithms at
> this time. We may try to be more sophisticated in the future.

> So, in short, please submit another bug and I'll add it to our queue.
> Please attach logs (especially where it shows the xds metadata as ebXML)
> .... as I think this just a problem with the overriding that did not get
> propegated to the bridge (but is in the underlying plugin).

> Also, we are at a conferece this week (which is why i'm working on
> Sunday). I'll attempt to attack your bug list ASAP, but just wanted to
> let the community know that we will be delayed this week.

> Regards,
> - Sarah

> Jesse Pangburn wrote:
>> 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 :-)
>>

Report message to a moderator

Re: confidentiality code when submitting CDA works strangely [message #37271 is a reply to message #36967]

Thu, 15 November 2007 19:49

No real name

Messages: 292
Registered: July 2009

Senior Member

Hi all,

This bug is fixed. Confidentiality code should now be the one provided
by the bridge user.

- Sarah

Jesse Pangburn wrote:
> Hi Sarah,
> I noticed the Sunday working thing, I was thinking "wow, IBM's got some
> serious slave drivers!" But a conference is understandable :-)
>
> So, I created Bug 209527
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=209527 for this. This
> one's easy enough for people to workaround for preliminary testing, just
> add the confidentiality code in the CDA.
>
> Thanks a bunch, enjoy your conference!
> Jesse
>
> Sarah Knoop wrote:
>
>> Hi Jesse,
>
>
>> You are on a roll :-) I think this is a problem that the bridge is not
>> overriding the confidentiality code as it should with the one provided
>> by the bridge user.
>
>
>> We do extract this information from the CDA ... however, metdata
>> extraction is imperfect for two reasons:
>> #1 XDS metadata for a submission cannot all be found in a CDA document
>> (scope problem).
>> #2 CDA requires different codes from different vocabularies than what
>> XDS metadata requires (termininology problem).
>
>
>> #2 is the problem that codes fall into ... so the bridge just
>> overrides these from user input rather than hooking ourselves up to
>> some terminology server or attempt sophisticated code mapping
>> algorithms at this time. We may try to be more sophisticated in the
>> future.
>
>
>> So, in short, please submit another bug and I'll add it to our queue.
>> Please attach logs (especially where it shows the xds metadata as
>> ebXML) .... as I think this just a problem with the overriding that
>> did not get propegated to the bridge (but is in the underlying plugin).
>
>
>> Also, we are at a conferece this week (which is why i'm working on
>> Sunday). I'll attempt to attack your bug list ASAP, but just wanted to
>> let the community know that we will be delayed this week.
>
>
>> Regards,
>> - Sarah
>
>
>
>
>
>> Jesse Pangburn wrote:
>>
>>> 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 :-)
>>>
>
>

Report message to a moderator