1 / 23

Implementing the XDS Infrastructure

Implementing the XDS Infrastructure. Bill Majurski IT Infrastructure National Institute of Standards and Technology. Focus. Repository Actor Registry Actor XDS.a XDS.b. Repository. 2 Styles File Server EHR (3) XDS Interfaces. Repository as a File Server.

bmoody
Télécharger la présentation

Implementing the XDS Infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing the XDS Infrastructure Bill Majurski IT Infrastructure National Institute of Standards and Technology

  2. Focus • Repository Actor • Registry Actor • XDS.a • XDS.b

  3. Repository • 2 Styles • File Server • EHR • (3) XDS Interfaces

  4. Repository as a File Server • Accepts files (documents) via Provide and Register transaction • Stores files for later retrieval

  5. EHR as Repository • Exposing content as Documents • Must generate size, hash for document • Must offer Document via URI • Must match size and hash

  6. Repository in XDS.a • SOAP (Register transaction) • HTTP Post • Body is XML • Top level element is SOAP-Envelope • SOAP with Attachments (Provide and Register transaction) • Body is MIME Multipart • First part is SOAP-Envelope • Additional parts are Documents

  7. …Repository in XDS.a Document Retrieve • HTTP GET • Be careful with MIME Type and size returned in HTTP Header • Size and Hash of body MUST match what was sent to Registry

  8. Repository in XDS.b Web Services interface changes • Provide and Register transaction • Namespaces • MTOM • Register transaction • Repository ID • uniqueID

  9. …Repository in XDS.b • Retrieve • Repository ID • uniqueID • Web service • Multiple documents

  10. XDS.a Register transaction • Send updated metadata to Registry • Via SOAP/WS message

  11. XDS.b Register transaction • Send metadata to Registry • Web service interface • ebRS/ebRIM version 3.0 • Can publish both • URI (XDS.a) • repositoryID / uniqueID (XDS.b)

  12. Registry • Functionality • Approaches • Interfaces • Validation

  13. Registry Functionality • Accept and Store metadata • Service Queries for metadata • Hard Parts • Parsing and generating metadata • Very complex XML • Validating metadata • Queries have many parameters

  14. XDS.a vs XDS.b • Details of SOAP wrapper • ebRIM/ebRS 2.1 vs 3.0 • Differentiate .a vs .b requests based on XML namespace • Stored query adds new optional parms, be able to ignore them

  15. Approaches to building a Registry • Start with open source ebXML Registry • Source Forge project ‘ebxmlrr’ • Add XDS functionality • Source Forge project ‘IheOs’ is example • Build on top of favorite database

  16. Registry Issues SQL Query (optional) • Raw SQL • Does assert database schema

  17. Registry - Validation • Metadata is archival content • As a community we must insure that metadata is ‘correct’ • ‘Correct’ • Key structural issues • Interpretable by any consumer • Heart of XDS

  18. Registry - Validation (2) • Registry Adaptor - functionality XDS adds to Registry standard • Specifies validation rules

  19. Testing • Pre-Connectathon (‘MESA’ tests) • Registry/Repository • Command line tools (Java) • Large corpus of test data • Submit (upload) results file to Kudu • Source/Consumer • Test against Public Registry • Connectathon • Use Stored Query to validate XDS tests

  20. Testing Related Profiles • ATNA testing is integrated • Node authentication • Audit log • At Connectathon - may want to be able to log to multiple Audit Repositories • Patient Identity Feed testing • Relies on PIX tests from MIR • XUA • Simple assertions to be tested in Stored Query and Retrieve Document Set • Consistent Time • Not tested as part of XDS

  21. Testing • New tools - easier to use • New tests - add detail

  22. Resources • IHE Wiki articles • http://wiki.ihe.net • Open Source implementation • Source Forge project ‘IheOs’ • Public Registry server • Runs ‘IheOs’ implementation

  23. …Resources • http://ihexds.nist.gov • Home page for XDS testing • Test definitions • FAQ • Documentation • bill@nist.gov

More Related