Embed Size (px)
DESCRIPTION
XDStarClient. Presentation of a suite of tools developed by IHE Europe for healthcare community Abderrazek Boufahja Mai 25, 2012. Menu. XDStar Functionality Systems Configuration Repositories configurations Registries configurations XCA RESP configurations epSOS - PowerPoint PPT Presentation
Citation preview
XDStarClientXDStarClient
Presentation of a suite of tools Presentation of a suite of tools developed by IHE Europe for developed by IHE Europe for
healthcare communityhealthcare community
Abderrazek BoufahjaAbderrazek Boufahja
Mai 25, 2012Mai 25, 2012
MenuMenu
• XDStar FunctionalityXDStar Functionality• Systems ConfigurationSystems Configuration
– Repositories configurationsRepositories configurations– Registries configurationsRegistries configurations– XCA RESP configurationsXCA RESP configurations
• epSOSepSOS– DispensationService:initialize()DispensationService:initialize()– ConsentService:put()ConsentService:put()– epSOS-1 transactionepSOS-1 transaction
• IHE /XDSIHE /XDS– Provide and register Set-bProvide and register Set-b– Registry Stored QueryRegistry Stored Query– Retrieve Document SetRetrieve Document Set– Cross Gateway QueryCross Gateway Query– Cross Gateway RetrieveCross Gateway Retrieve
• WS ValidationWS Validation– XDStar ws validationXDStar ws validation– EVSClient validationEVSClient validation
XDStar functionalityXDStar functionality
• XDStarClient is a tool based on IHE / epSOS specifications XDStarClient is a tool based on IHE / epSOS specifications for XDS transactionsfor XDS transactions
• Fonctionalities : Fonctionalities : – Simulation of epSOS transactions (PatientService, OrderService, Simulation of epSOS transactions (PatientService, OrderService,
ConsentService, IdentificationService)ConsentService, IdentificationService)
– Simulation of IHE / XDS transactions (Provide and Register Set-b, Simulation of IHE / XDS transactions (Provide and Register Set-b, Registry Stored Query, Retrieve Docuement Set, Cross Gateway Registry Stored Query, Retrieve Docuement Set, Cross Gateway Query, Cross Gateway Retrieve)Query, Cross Gateway Retrieve)
– Validation of all transactions done by the toolValidation of all transactions done by the tool
– WS validation of epSOS/ IHE XDS metadatasWS validation of epSOS/ IHE XDS metadatas
Systems configurationsSystems configurations
There are three type of configurations supported by There are three type of configurations supported by XDStar : XDStar :
• Repositories configurationsRepositories configurations• Registries configurationsRegistries configurations• XCA Responding Gateway configurationsXCA Responding Gateway configurations
The configurations of Document recipient for XDR The configurations of Document recipient for XDR profile are integrated to the repositories profile are integrated to the repositories configurationsconfigurations
Repositories configurationsRepositories configurations
• Repositories can be configured by going to the menu : Repositories can be configured by going to the menu : – SUT Configurations SUT Configurations Repositories configurations Repositories configurations
– To add a new configuration, you have to loginTo add a new configuration, you have to login
Registries configurationsRegistries configurations
• Registries can be configured by going to the menu : Registries can be configured by going to the menu : – SUT Configurations SUT Configurations Registries configurations Registries configurations
– To add a new configuration, you have to loginTo add a new configuration, you have to login
XCA RESP configurationsXCA RESP configurations
• Registries can be configured by going to the menu : Registries can be configured by going to the menu : – SUT Configurations SUT Configurations XCA-Responding-Gateway-Configurations XCA-Responding-Gateway-Configurations
– To add a new configuration, you have to loginTo add a new configuration, you have to login
DispensationService:initialize()[1]DispensationService:initialize()[1]
• How to access : menu How to access : menu Simulators Simulators epSOS epSOS DispentationService:initialize()DispentationService:initialize()
• Configurations that can Configurations that can be selected : Repositories configurationsbe selected : Repositories configurations• Optionality : Optionality :
– Upload files to register : upload one or many dispensation document to be sent to the Upload files to register : upload one or many dispensation document to be sent to the repositoryrepository
– Generate file to register : use a preloaded document from the server, and sent it to the Generate file to register : use a preloaded document from the server, and sent it to the repositoryrepository
DispensationService:initialize()[2]DispensationService:initialize()[2]
• Metadatas : Metadatas : – XDSSubmissionSet.authorXDSSubmissionSet.author– XDSSubmissionSet.contentTypeCodeXDSSubmissionSet.contentTypeCode– XDSSubmissionSet.patientIdXDSSubmissionSet.patientId– XDSSubmissionSet.sourceId : its value is defined as a parameter of the XDSSubmissionSet.sourceId : its value is defined as a parameter of the
applicationapplication– XDSSubmissionSet.uniqueId : a unique id generated by the application for XDSSubmissionSet.uniqueId : a unique id generated by the application for
the SubmissionSetthe SubmissionSet
• For this transaction, this simulator support : For this transaction, this simulator support : – XUA : insert of assertionsXUA : insert of assertions– ATNA : secure communicationATNA : secure communication
DispensationService:initialize()[3]DispensationService:initialize()[3]
• Sending of the documents : you can send your documents by Sending of the documents : you can send your documents by clicking on the button clicking on the button ExecuteExecute. The execution generate a . The execution generate a message that contains the date of execution, the transaction message that contains the date of execution, the transaction name, the affinity domain, the message type, the response name, the affinity domain, the message type, the response code, the responder name, and finally the request and the code, the responder name, and finally the request and the response and their validationsresponse and their validations
• The list of validated message can be found on the menu : The list of validated message can be found on the menu : messages messages Provide and Register Set-b messages Provide and Register Set-b messages
DispensationService:initialize()[4]DispensationService:initialize()[4]
• There are two buttons that can be used, on the column action : There are two buttons that can be used, on the column action : view the content of the metadatas sent, and the response of the repository view the content of the metadatas sent, and the response of the repository
validate the content of metadatas sent and validate the responsevalidate the content of metadatas sent and validate the response
• There There are three buttons on request/resp messages columns : are three buttons on request/resp messages columns : – Validation is not well, there are errors on validationValidation is not well, there are errors on validation– Validation is well done, no errors on the validationValidation is well done, no errors on the validation– There are no validation done, if you want you can do one, by clicking hereThere are no validation done, if you want you can do one, by clicking here
ConsentService:put()[1]ConsentService:put()[1]
• How to access : How to access : menu menu Simulators Simulators ConsentService:put() ConsentService:put()• Configurations that can be selected : Configurations that can be selected : Repositories configurationsRepositories configurations• Policy Policy : Opt-in, Opt-out : Opt-in, Opt-out • Optionality : Optionality :
– Upload files to register : upload one or many consent document to be sentUpload files to register : upload one or many consent document to be sent– Generate file to register : use a preloaded document from the server, and sent itGenerate file to register : use a preloaded document from the server, and sent it
ConsentService:put()[2]ConsentService:put()[2]
• Metadatas : Metadatas : – XDSSubmissionSet.authorXDSSubmissionSet.author– XDSSubmissionSet.contentTypeCodeXDSSubmissionSet.contentTypeCode– XDSSubmissionSet.patientIdXDSSubmissionSet.patientId– XDSSubmissionSet.sourceId : its value is defined as a parameter of the XDSSubmissionSet.sourceId : its value is defined as a parameter of the
applicationapplication– XDSSubmissionSet.uniqueId : a unique id generated by the application for XDSSubmissionSet.uniqueId : a unique id generated by the application for
the SubmissionSetthe SubmissionSet
• For this transaction, this simulator support : For this transaction, this simulator support : – XUA : insert of assertionsXUA : insert of assertions– ATNA : secure communicationATNA : secure communication
ConsentService:put()[3]ConsentService:put()[3]
• As for DispensationService:initialize(), the As for DispensationService:initialize(), the ConsentService:put() has the same behavior for executing ConsentService:put() has the same behavior for executing the sent of the message to the repository, the GUI of the the sent of the message to the repository, the GUI of the messages sent and received. We can also validate these messages sent and received. We can also validate these messages using the button validate from the action messages using the button validate from the action column.column.
epSOS-1 transaction [1]epSOS-1 transaction [1]
• epSOS-1 transaction is composed from 4 types of message types :epSOS-1 transaction is composed from 4 types of message types :– OrderService:listOrderService:list
– OrderService:retrieveOrderService:retrieve
– PatientService:listPatientService:list
– PatientService:retrievePatientService:retrieve
• OrderService:list and PatientService:list are the transaction ITI-38 OrderService:list and PatientService:list are the transaction ITI-38 on the affinityDomain epSOS. To create the request, you have to on the affinityDomain epSOS. To create the request, you have to fill some metadatas, and that depend to the transaction used. fill some metadatas, and that depend to the transaction used.
epSOS-1 transaction [2]epSOS-1 transaction [2]
• On the PatientService:retrieve and the OrderService:retrieve, On the PatientService:retrieve and the OrderService:retrieve, the user have to fill the homeCommunityId, the repositoryId, and the user have to fill the homeCommunityId, the repositoryId, and the uniqueId of the document to retrieve.the uniqueId of the document to retrieve.
• All the four messageType support XUA and ATNA, secured All the four messageType support XUA and ATNA, secured endpoint are supportedendpoint are supported
Provide and register Set-b[1]Provide and register Set-b[1]
• How to access from menu : Simulators How to access from menu : Simulators IHE IHE ITI-41 [Provide ITI-41 [Provide and Register Set-b]and Register Set-b]
• The aim of this page is to provide for the user a tool to submit The aim of this page is to provide for the user a tool to submit folders and XDSDocuments to a repository with the correct folders and XDSDocuments to a repository with the correct association between SubmissionSet, folders, && documents.association between SubmissionSet, folders, && documents.
• After selecting a repository, a tree representing the content of After selecting a repository, a tree representing the content of the submission appears in the GUI : the submission appears in the GUI :
Provide and register Set-b[2]Provide and register Set-b[2]
• To add document to a submissionSet or to a folder, you have to click on To add document to a submissionSet or to a folder, you have to click on the button . This will update the GUI and view a list of metadatas the button . This will update the GUI and view a list of metadatas related to the XDSDocumentEntry addedrelated to the XDSDocumentEntry added
• To add a new folder to a submissionSet, you have to click on the button To add a new folder to a submissionSet, you have to click on the button . This will update the GUI with metadatas of the XDSFolder added. . This will update the GUI with metadatas of the XDSFolder added.
• The list of metadatas that the user can choose are uploaded by the tool The list of metadatas that the user can choose are uploaded by the tool from the SVS repository of IHE europe.from the SVS repository of IHE europe.
• To add optional metadatas, you have to click on the button To add optional metadatas, you have to click on the button ““Add Add Optional MetadataOptional Metadata””
Provide and register Set-b[3]Provide and register Set-b[3]
• To execute the submissionSet, you have to click on the button To execute the submissionSet, you have to click on the button ExecuteExecute
• The result of the execution appears on the GUI as a table The result of the execution appears on the GUI as a table containing the request, the response, and the response code.containing the request, the response, and the response code.
• To validate the request || the response, you have to click on the To validate the request || the response, you have to click on the button validate on the action column. A popup will show the button validate on the action column. A popup will show the result of the validation.result of the validation.
Registry Stored Query [1]Registry Stored Query [1]
• Access from the menu : SimulatorsAccess from the menu : Simulators IHE IHE ITI-18 [Registry ITI-18 [Registry Stored Query].Stored Query].
• The registry stored query is a set of messages types, that can The registry stored query is a set of messages types, that can be selected from the GUIbe selected from the GUI
Registry Stored Query [2]Registry Stored Query [2]
• To create an ITI-18 query, the user have to fill the list of To create an ITI-18 query, the user have to fill the list of metadata generated from the messageType selected :metadata generated from the messageType selected :
• To add optional parameter to the request, you have to click on To add optional parameter to the request, you have to click on the button the button addOptionalParameter addOptionalParameter : :
Retrieve Document Set[1]Retrieve Document Set[1]
• How to access from menu : Simulators How to access from menu : Simulators IHE IHE ITI-43 ITI-43 [Retrieve Document Set][Retrieve Document Set]
• To execute the request you have to select a repository To execute the request you have to select a repository configurationconfiguration
Retrieve Document Set[2]Retrieve Document Set[2]
• Retrieve Document Set is a simple request based on three Retrieve Document Set is a simple request based on three parameters : HomeCommunityId, RepositoryUniqueId, and parameters : HomeCommunityId, RepositoryUniqueId, and DocumentUniqueIdDocumentUniqueId
• ToTo• To Execute the retrieve request, you have to click on To Execute the retrieve request, you have to click on ExecuteExecute• You can preview the message to be sent by clicking on You can preview the message to be sent by clicking on PreviewPreview
Cross Gateway Query[1]Cross Gateway Query[1]
• Access from the menu : Simulators Access from the menu : Simulators IHE IHE Cross Gateway Query Cross Gateway Query
• From the GUI, we have to select first the registry configuration, then we From the GUI, we have to select first the registry configuration, then we have to select the message type to executehave to select the message type to execute
Cross Gateway Query[2]Cross Gateway Query[2]
• For each messageType, a list of required metadatas are For each messageType, a list of required metadatas are rendered on the GUIrendered on the GUI
• To add optional metadata, you have to click on the button “To add optional metadata, you have to click on the button “Add Add Optional ParameterOptional Parameter””
Cross Gateway RetrieveCross Gateway Retrieve
• Access from the menu : Simulators Access from the menu : Simulators IHE IHE Cross Gateway RetrieveCross Gateway Retrieve
• Cross Gateway retrieve is based on the transaction Retrieve Document Cross Gateway retrieve is based on the transaction Retrieve Document Set. The GUI is almost the same.Set. The GUI is almost the same.
WS ValidationWS Validation
• Link :Link :http://gazelle.ihe.net/XDStarClientWS/XDSMetadataValidatorWS?wsdl
• Methods :Methods :– validateXDStarMetadata : validate a text document using a type of validatorvalidateXDStarMetadata : validate a text document using a type of validator
– validateXDStarMetadataB64 : validate a base 64 document using a type of validatorvalidateXDStarMetadataB64 : validate a base 64 document using a type of validator
– getListEPSOSValidator : return a list of validators for epSOS domaingetListEPSOSValidator : return a list of validators for epSOS domain
– getListIHEValidator : return a list of validator for IHE domaingetListIHEValidator : return a list of validator for IHE domain
• Technologies Technologies : XDS validation is based on model driven architecture. We : XDS validation is based on model driven architecture. We define a model to describe the content of the XDS metadata document, then define a model to describe the content of the XDS metadata document, then we populate the model by UML constraints, using OCL language (Object we populate the model by UML constraints, using OCL language (Object Constraint language). Constraints are extract from the TF of IHE && epSOS.Constraint language). Constraints are extract from the TF of IHE && epSOS.
EVSClient Validation [1]EVSClient Validation [1]
• The WS of XDStarClient is used by EVSClient to validate epSOS / IHE The WS of XDStarClient is used by EVSClient to validate epSOS / IHE XDS metadata. To Access to this validator from EVSClient menu, you XDS metadata. To Access to this validator from EVSClient menu, you have to go to XDS have to go to XDS epSOS / IHE epSOS / IHE validate validate
EVSClient Validation [2]EVSClient Validation [2]
• The validation of the metadata contains two level : schema The validation of the metadata contains two level : schema validation and content validation, based on model driven validation and content validation, based on model driven constraints.constraints.
EVSClient Validation [3]EVSClient Validation [3]
• All validated metadata request / response are stored on the All validated metadata request / response are stored on the database. An advanced search tool is implemented for users for database. An advanced search tool is implemented for users for dynamic search of already validated documentsdynamic search of already validated documents
XDStarClientXDStarClient
Presentation of a suite of tools Presentation of a suite of tools developed by IHE Europe for developed by IHE Europe for
healthcare communityhealthcare community
Abderrazek BoufahjaAbderrazek Boufahja
Mai 25, 2012Mai 25, 2012
