NIST Registry

11 views
Skip to first unread message

Bill Majurski

unread,
Jan 11, 2007, 11:19:14 AM1/11/07
to ihe...@rsna.org
Some folks were having problems accessing the NIST Registry. It is
back up and running.

bill

Bill Majurski

unread,
Jan 11, 2007, 1:05:14 PM1/11/07
to Juggy Jagannathan, ihe...@rsna.org
The Public Registry will not be configured with Connectathon certificates. It will continue to run with the Pre-Connecathon certs.

bill


On Jan 11, 2007, at 5:58 PM, Juggy Jagannathan wrote:

Is it configured to accept the new certificates?

- regards
- juggy
V. "Juggy" Jagannathan, PhD
Vice President Of Research
Assoc Prof, West Virginia University
235 High Street, Suite 2I3, Morgantown, WV 26505
Phone: 304.296.7550 ext. 101
Fax: 304.296.5038
Cell: 304.685.3298

"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit."

Helen Keller
ju...@medquist.com
www.medquist.com

<C5734216.gif>

This electronic mail transmission contains confidential information intended only for the person(s) named.
Any use, distribution, copying or disclosure by another person is strictly prohibited.
If you are not the intended recipient of this e-mail, promptly delete it and all attachments.

<graycol.gif>
Bill Majurski <bi...@nist.gov>


<ecblank.gif>

To
<ecblank.gif>

ihe...@rsna.org
<ecblank.gif>

cc
<ecblank.gif>

<ecblank.gif>

Subject
<ecblank.gif>

NIST Registry
<ecblank.gif>
<ecblank.gif>

Juggy Jagannathan

unread,
Jan 11, 2007, 12:58:53 PM1/11/07
to Bill Majurski, ihe...@rsna.org

Is it configured to accept the new certificates?

- regards
- juggy
V. "Juggy" Jagannathan, PhD
Vice President Of Research
Assoc Prof, West Virginia University
235 High Street, Suite 2I3, Morgantown, WV 26505
Phone: 304.296.7550 ext. 101
Fax: 304.296.5038
Cell: 304.685.3298

"No pessimist ever discovered the secret of the stars, or sailed to an uncharted land, or opened a new doorway for the human spirit."

This electronic mail transmission contains confidential information intended only for the person(s) named.
Any use, distribution, copying or disclosure by another person is strictly prohibited.
If you are not the intended recipient of this e-mail, promptly delete it and all attachments.

Inactive hide details for Bill Majurski <bill@nist.gov>Bill Majurski <bi...@nist.gov>



To

ihe...@rsna.org

cc


Subject

NIST Registry

Glenn Deen

unread,
Jan 11, 2007, 1:13:18 PM1/11/07
to Bill Majurski, ihe...@rsna.org, Juggy Jagannathan

Hi Bill,

I'm loosing track of the various Cert sets we have floating around.  Which pre-connectathon certs is NIST using - certainly not the test certs which expired in Dec 06.



Glenn Deen, Computer Science
IBM Almaden Research Center - San Jose California
gl...@almaden.ibm.com (408)927-3910/(tie)457-3910



Bill Majurski <bi...@nist.gov>

01/11/2007 10:05 AM

Please respond to
Bill Majurski <bi...@nist.gov>

To
Juggy Jagannathan <Ju...@medquist.com>
cc
ihe...@rsna.org
Subject
Re: NIST Registry


Nuno Pina Cabral

unread,
Jan 12, 2007, 11:34:11 AM1/12/07
to Bill Majurski, ihe...@rsna.org, Paulo....@mni.pt, Agostinho Gomes, Artur Mesquita, Catherine Glenz
Hello,

We have been testing with NIST registry.
When we query for documents given an user Id we receive the following type
of response.

<SQLQueryResult>
<rim:ObjectRef id="urn:uuid:7a525a92-3786-401f-8077-e0645dd9f3a4"
xmlns:q="urn:oasis:names:tc:ebxml-regrep:query:xsd:2.1"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.1"/>
<rim:ObjectRef id="urn:uuid:50d53c93-2867-4fe8-98c3-924eacfb8f72"
xmlns:q="urn:oasis:names:tc:ebxml-regrep:query:xsd:2.1"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.1"/>
<rim:ObjectRef id="urn:uuid:163fd0a9-9605-4872-b51d-dc489b317cfb"
xmlns:q="urn:oasis:names:tc:ebxml-regrep:query:xsd:2.1"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.1"/>
<rim:ObjectRef id="urn:uuid:000a745b-face-41b5-b869-ebbde1133d36"
xmlns:q="urn:oasis:names:tc:ebxml-regrep:query:xsd:2.1"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.1"/>
</SQLQueryResult>


The question is: How do we resolve these "id" Attribute Values to URIs?
Shouldn't an URI contain also information like protocol and protocol
parameters that are to be used to retrieve the document?...

Thank you and Best regards,

Nuno

Nuno Pina Cabral

unread,
Jan 12, 2007, 10:59:29 AM1/12/07
to Bill Majurski, ihe...@rsna.org, Agostinho Gomes, Paulo....@mni.pt, Artur Mesquita, Catherine Glenz
Hello,

We have been testing with NIST registry and things are running smoothly.
We are using a query that retrieves available doc URI given a Patient Id:

SELECT eo.id
FROM ExtrinsicObject eo, ExternalIdentifier ei
WHERE eo.id = ei.registryobject AND

ei.identificationScheme='urn:uuid:58a6f841-87b3-4a3e-92fd-a8ffeff98427' AND
ei.value='NIST-query-2^^^&amp;1.3.6.1.4.1.21367.2005.3.7&amp;ISO'
AND
eo.status = 'Approved'

We would also like to receive some description data related to each document
to present to the clinicians (for instance title/type) - so they can pickup
the documents they want to display.
Is this possible? If so, what would be the query to get this description
data?

Thank you and best regards,

Nuno


Reply all
Reply to author
Forward
0 new messages