Page tree
Skip to end of metadata
Go to start of metadata

The OpenNCP software now includes an "Automated Testing Tool". The whole purpose of this tool is to aid PNs to assess the conformance of their NCP instances by automatically validating all the transaction, audit messages and the related CDA documents.

In this page you can find a set of instructions that will help you use this validation capabilities through this tool. Please leave your comment at the bottom of this page or create an issue if you experience any issue with the usage of the tool.

You can find more information about this tool and the testing strategy in the following page "Integration of CI Environment With Gazelle Services". 

Table of contents:

1. How the tool works

This tool makes use of remote validation capabilities, provided by IHE, to perform a validation of several objects that the NCP uses in the multiple services workflows.

It will automatically extract the required objects (such as transaction, audit messages and CDA documents) and apply the correct validators to them.

It is a bit like what is performed during a PPT and PAT testing fases, using the Gazelle EVS tool. But this time in a fully automated way.

The tool will generate a set of validation reports with valuable information about the validation process - the content of this reports will be explained further in this page.

Please note

This tool will not produce EVS permanent links, as it seats at the same level as EVS Client (which is also a web client for IHE services). It will produce real time validation results based on IHE validators, that you can use to understand your NCP unconformace and fine tune it.

 

2. How can it be set to work

At the moment this tool requires very few configuration steps, being the most significant ones the turn on/off switch and the validation folder setup.

a. In order to turn on this validation capabilities you need to add a new epsos.properties database property called

automated.validation

Assigning the value true or false will either turn On of Off the automated validation.

b. The second aspect that you may need to adjust is:

  • Create a folder called "validation" under EPSOS_PROPS_PATH and configure it with the right permissions for the application server user (e.g. read/write);

This step might be not necessary, since the application is configured to create the directory. But if you feel that the directory is not being created please create it and set the right permissions.

Example of validation directory structure:

EPSOS_PROPS_PATH
`-- VALIDATION
	`-- NCP-A
	|   |-- VALIDATION_REPORT_#1
	|   |-- VALIDATION_REPORT_#2   
	|   `-- VALIDATION_REPORT_#3   
	`-- NCP-B
    	|-- VALIDATION_REPORT_#1
	    |-- VALIDATION_REPORT_#2   
    	`-- VALIDATION_REPORT_#3

Optional firewall configuration

Depending on your NCP environment you may need to adjust your firewall opening for requests in the 8080 port, required by the remote validation services. You can find the used addresses in the table below

AddressPort
jumbo.irisa.fr8080
131.254.209.208080

With these two options configured you should be able to obtain some validation reports, once you start performing the normal workflows.

3. What kind of results are produced

3.1. File naming structure

The report file names will have the following structure:

[ time stamp ]_[ validated object type ]_[ used validation model ]_[ validation result ].xml

Example:

20131125122818452_XCA-RETRIEVE-RESPONSE_EPSOS-2-FETCHDOCUMENTSERVICE-RETRIEVE---RESPONSE_PASSED.xml

3.2. Validation report content

The validation reports have the following structure:

<validationReport>This is the main node of the validation report, all the information is contained inside this node.
<validatedObject>This node contains the object submitted to validation. It can be an Audit Message, an XD* transaction message or others.
<validationResult>This node contains the validation summary of the validated object. It is basically the information returned by IHE remote validator. In this node you will find useful information about the validation result, the obtained errors (if any) and other information.

For instance, you can look for the validation result in:

validationReport/validationReport/detailedResult/validationResultsOverview/validationRestResult

You can easily extract the validated object with the following command:

sudo sed -n '/<validatedObject*/, /<\/validatedObject>/p' 20140408111734978_AUDIT_EPSOS-2---FETCH-DOCUMENT-SERVICE-\(SERVICE-PROVIDER\)_PASSED.xml | egrep -v 'validatedObject' > 'filename.xml'

 

Or you can use the following script, that will extract all the objects from all the validation reports presented in a folder. You just need to execute it inside the validation folder (e.g. NCP-A, NCP-B). You will have the same file names, with ".cleared" extension.

  File Modified
File clean_files.sh Apr 09, 2014 by Marcelo Fonseca

 

You can check for validation errors in:

validationReport/validationResult/detailedResult/MDAValidation

Example

Example of validation report for a "Fetch Documents Query Request" message (XCA Query Request)
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<validationReport>
<validatedObject>
<ns3:AdhocQueryRequest
   xmlns="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"
   xmlns:ns2="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"
   xmlns:ns3="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"
   xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:ns5="urn:ihe:iti:xds-b:2007">
   <ns3:ResponseOption returnComposedObjects="true" returnType="LeafClass"/>
   <AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
      <Slot name="$XDSDocumentEntryPatientId">
         <ValueList>
            <Value>'182581814^^^&amp;2.16.620.1.101.10.1.1&amp;ISO'</Value>
         </ValueList>
      </Slot>
      <Slot name="$XDSDocumentEntryStatus">
         <ValueList>
            <Value>('urn:oasis:names:tc:ebxml-regrep:StatusType:Approved')</Value>
         </ValueList>
      </Slot>
      <Slot name="$XDSDocumentEntryClassCode">
         <ValueList>
            <Value>('56445-0^^2.16.840.1.113883.6.1')</Value>
         </ValueList>
      </Slot>
   </AdhocQuery>
</ns3:AdhocQueryRequest>
</validatedObject>
<validationResult>
<detailedResult>
    <DocumentValidXSD>
        <Result>PASSED</Result>
    </DocumentValidXSD>
    <DocumentWellFormed>
        <Result>PASSED</Result>
    </DocumentWellFormed>
    <MDAValidation>
        <Note>
            <Test>constraint_epsos2_FormatCodeValues</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryFormatCode's values SHALL be from the valueSet 1.3.6.1.4.1.12559.11.4.1.3 http://gazelle.ihe.net/RetrieveValueSet?id=1.3.6.1.4.1.12559.11.4.1.3  (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_FormatCodeValues</Identifiant>
        </Note>
        <Note>
            <Test>constraint_epsos2_XDSDocumentEntryPatientId</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : XDSDocumentEntryPatientId MUST provide the HL7v3 II coded patient identifier (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_XDSDocumentEntryPatientId</Identifiant>
        </Note>
        <Note>
            <Test>constraint_epsos2_XDSDocumentEntryType</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryType's value SHALL be 'urn:uuid:34268e47-fdf5-41a6-ba33-82133c465248' or 'urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1' (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_XDSDocumentEntryType</Identifiant>
        </Note>
        <Note>
            <Test>constraint_epsos2_classCodeValues</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryClassCode's values SHALL be from the valueSet  1.3.6.1.4.1.12559.11.4.1.5 http://gazelle.ihe.net/RetrieveValueSet?id=1.3.6.1.4.1.12559.11.4.1.5  (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_classCodeValues</Identifiant>
        </Note>
        <Note>
            <Test>constraint_epsos2_possiblemetadatas</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : Possible metadatas  in findDocuments in epSOS-2 transaction / request, are $XDSDocumentEntryPatientId, $XDSDocumentEntryClassCode, $XDSDocumentEntryStatus, $XDSDocumentEntryFormatCode, $XDSDocumentEntryType (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_possiblemetadatas</Identifiant>
        </Note>
        <Note>
            <Test>constraint_epsos2_requiredmetadatas</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : required metadatas in findDocuments in epSOS-2 transaction / request, are $XDSDocumentEntryPatientId, $XDSDocumentEntryClassCode, $XDSDocumentEntryStatus (WP3A_epSOS_EED_IHE_XCA_Binding, 2.1) </Description>
            <Identifiant>EPSOS2XCAReq-epSOS2FindDocuments-constraint_epsos2_requiredmetadatas</Identifiant>
        </Note>
        <Note>
            <Test>constraintQueryID</Test>
            <Location>/AdhocQueryRequest</Location>
            <Description>Note :  This condition was verified : QueryID must be one from the table 3.18.4.1.2.4 from the ITI TF-2a </Description>
            <Identifiant>rsqihe-RSQIHEConstraints-constraintQueryID</Identifiant>
        </Note>
        <Note>
            <Test>constraintReturnType</Test>
            <Location>/AdhocQueryRequest</Location>
            <Description>Note :  This condition was verified : the return type must be LeafClass or ObjectRef (ITI TF-2a, 3.18.4.1.2.3) </Description>
            <Identifiant>rsqihe-RSQIHEConstraints-constraintReturnType</Identifiant>
        </Note>
        <Note>
            <Test>constraintFindDocuments_allowedSlot</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : allowed metadata are only ones detailed on the TF 2a,  3.18.4.1.2.3.7.1 </Description>
            <Identifiant>rsqihe-FindDocuments-constraintFindDocuments_allowedSlot</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryAuthorPerson_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryAuthorPerson does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryAuthorPerson_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryClassCode_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryClassCode does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryClassCode_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryCreationTimeFrom_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryCreationTimeFrom is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryCreationTimeFrom_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryCreationTimeFrom_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryCreationTimeFrom does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryCreationTimeFrom_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryCreationTimeTo_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryCreationTimeTo is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryCreationTimeTo_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryCreationTimeTo_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryCreationTimeTo does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryCreationTimeTo_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryFormatCode_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryFormatCode does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryFormatCode_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryHealthcareFacilityTypeCode_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryHealthcareFacilityTypeCode does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryHealthcareFacilityTypeCode_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryPatientId_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryPatientId is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryPatientId_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryPatientId_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryPatientId does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryPatientId_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryPatientId_required</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryPatientId is required on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryPatientId_required</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryPracticeSettingCode_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryPracticeSettingCode does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryPracticeSettingCode_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStartTimeFrom_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStartTimeFrom is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStartTimeFrom_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStartTimeFrom_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStartTimeFrom does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStartTimeFrom_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStartTimeTo_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStartTimeTo is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStartTimeTo_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStartTimeTo_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStartTimeTo does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStartTimeTo_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStopTimeFrom_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStopTimeFrom is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStopTimeFrom_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStopTimeFrom_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStopTimeFrom does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStopTimeFrom_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStopTimeTo_notMultiple</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStopTimeTo is not multivalued on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStopTimeTo_notMultiple</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryServiceStopTimeTo_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryServiceStopTimeTo does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryServiceStopTimeTo_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryStatus_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryStatus does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryStatus_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryStatus_required</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryStatus is required on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryStatus_required</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryTypeCode_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryTypeCode does not support AND/OR on FindDocuments MessageType (ITI TF-2a 3.18.4.1.2.3.7.1)) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryTypeCode_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryType_notSupportAND</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : $XDSDocumentEntryType does not support AND/OR on FindDocuments MessageType (ITI TF-2a, IHE_ITI_Suppl_On_Demand_Documents, 3.18.4.1.2.3.7.1) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryType_notSupportAND</Identifiant>
        </Note>
        <Note>
            <Test>constraintITI18_XDSDocumentEntryType_values</Test>
            <Location>/AdhocQueryRequest/AdhocQuery</Location>
            <Description>Note :  This condition was verified : allowed values on $XDSDocumentEntryType metadatas are urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1 and urn:uuid:34268e47-fdf5-41a6-ba33-82133c465248 (ITI TF-2a, IHE_ITI_Suppl_On_Demand_Documents, 3.18.4.1.2.3.6.2) </Description>
            <Identifiant>rsqihe-FindDocuments-constraintITI18_XDSDocumentEntryType_values</Identifiant>
        </Note>
        <Result>PASSED</Result>
    </MDAValidation>
    <ValidationResultsOverview>
        <ValidationDate>2013, 11 14</ValidationDate>
        <ValidationTime>04:26:39</ValidationTime>
        <ValidationServiceName>Gazelle XDSMetadata Validation</ValidationServiceName>
        <ValidationTestResult>PASSED</ValidationTestResult>
    </ValidationResultsOverview>
</detailedResult>
</validationResult>
</validationReport>

 

4. Which objects are currently validated

Currently the following objects are being submitted to IHE validators:

HL7v3

epSOS Identification Service (Request)This message represents the request used in the Identification Service
epSOS Identification Service (Response)This message represents the response used in the Identification Service

XD*

epSOS-2 Fetch Document Service Query (Request)This message represents the Fetch Document Service Query Request, used in multiple epSOS services, like Patient Service, Order Service, MRO Service and PAC.
epSOS-2 Fetch Document Service Query (Response)This message represents the Fetch Document Service Query Response, used in multiple epSOS services, like Patient Service, Order Service, MRO Service and PAC.
epSOS-2 Fetch Document Service Retrieve (Request)This message represents the Fetch Document Service Retrieve Request, used in multiple epSOS services, like Patient Service, Order Service, MRO Service and PAC.
epSOS-2 Fetch Document Service Retrieve (Response)This message represents the Fetch Document Service Retrieve Reponse, used in multiple epSOS services, like Patient Service, Order Service, MRO Service and PAC.
epSOS-2 Provide Data Service (Request)This message represents the Provide Data Service Data Request, used in multiple epSOS services, like Dispensation Service, Consent Service and HCER Service. 
epSOS-2 Provide Data Service (Response)This message represents the Provide Data Service Data Response, used in multiple epSOS services, like Dispensation Service, Consent Service and HCER Service.

Audit

epSOS-2 - Identification Service Audit (Service Provider)This audit message is produced in NCP-A during the Identification Service workflow execution.
epSOS-2 - HCP Assurance AuditThis audit message is produced in NCP-B during the Identification Service workflow execution.
epSOS-2 - Fetch Document Service (Service Consumer)This audit message is produced in NCP-B during the Patient Service, Order Service, MRO Service and PAC.
epSOS-2 - Fetch Document Service (Service Provider)This audit message is produced in NCP-A during the Patient Service, Order Service, MRO Service and PAC.
epSOS-2 - Provide Data Service (Service Consumer)This audit message is produced in NCP-B during the Dispensation Service, Consent Service and HCER Service.
epSOS-2 - Provide Data Service (Service Provider)This audit message is produced in NCP-A during the Dispensation Service, Consent Service and HCER Service.

CDA Documents

epSOS - HCER HealthCare Encounter ReportThis is the Model Based validation for the Health-care Encounter Report CDA document.
epSOS - MRO Medication Related OverviewThis is the Model Based validation for the Medication Related Overview CDA document.
epSOS - Patient Summary FriendlyThis is the Model Based validation for the Patient Summary (Friendly version) CDA document.
epSOS - Patient Summary PivotThis is the Model Based validation for the Patient Summary (Pivot version) CDA document.
epSOS - Scanned DocumentThis is the Model Based validation for the Scanned Document CDA document.
epSOS - eConsentThis is the Model Based validation for the Consent CDA document.
epSOS - eDispensation FriendlyThis is the Model Based validation for the eDispensation (Friendly version) CDA document.
epSOS - eDispensation PivotThis is the Model Based validation for the eDispensation (Pivot version) CDA document.
epSOS - ePrescription FriendlyThis is the Model Based validation for the ePrescription (Friendly version) CDA document.
epSOS - ePrescription PivotThis is the Model Based validation for the ePrescription (Pivot version) CDA document.

5. Best usage practices

The usage of this tool will apply some workload in the IHE validation services together with the creation of multiple validation files in your NCP environment as-well. Therefore we have defined the following best practices for the usage of this tool:

  • The default option for the validation tool switch should be OFF;
  • We recommend you to previously prepare the testing session, turn on the automated validation, perform the required workflows, turn off the validation and finally interpret the results;
  • Please keep your validation folder maintained and organized as it can grow quickly, eventually leading you to loose trace of important reports;
  • If you have any comment please write it at the bottom of this page or in case of an experienced problem, please create a new issue in OpenNCP project and assign it to ;

6. FAQ

I have set up the validation tool, including the firewall opening for port 8080 but I still cannot obtain the validation reports

One possible cause for this situation is the possible existent IPSec configuration to establish VPN connection with IHE. Try to disable this IPSec connection and test again. If the problem persists please submit your issue.

7. Related articles

Error rendering macro 'contentbylabel' : parameters should not be empty

2 Comments

  1. Awesome!!! please keep up with this value added work!

  2. I agree, this package of work and the documentation is second to none!