XIS maintenance - Revision history

Admin: /* Setting up a testaccount */

2020-07-13T21:30:03Z

‎Setting up a testaccount

2018-12-03T10:25:49Z

‎Introduction to XIS

2018-12-03T10:14:54Z

‎Configuring query parameters: Testsuite schematron to check payload

2015-08-25T12:14:09Z

‎Using variables in templates: typo

2015-08-25T11:21:17Z

‎Using variables in templates

2015-08-25T11:13:20Z

‎Variables typically used in message payload

2015-08-25T11:10:09Z

‎Using variables in templates

2015-08-25T11:09:55Z

‎Using variables in templates

2015-08-25T10:49:46Z

‎Response templates

2015-08-25T10:49:13Z

‎Response templates

@@ Line 37: / Line 37: @@
 * save: saves the testaccount configuration
 Screenshot for the configuration of a testaccount:
 [[Image:En_xis_testaccount_configure.png|800px]]
 == Connectivity description ==
 The following content is handled by the XIS-server:

@@ Line 1: / Line 1: @@
 == Introduction to XIS ==
 XIS functions as a testserver which can be used to test remote applications: validate messages/documents or uploaded files.
 Depending on the testscript the following situations are possible:
@@ Line 9: / Line 11: @@
 ** The remote application returns content or (n)ack to the XIS-server
 * The messages are manually uploaded with XIS
 == Setting up a testaccount ==
 Before starting a test, a testaccount should be configured:

← Older revision		Revision as of 10:14, 3 December 2018
Line 358:		Line 358:
	</queryManifest>		</queryManifest>
	</syntaxhighlight>		</syntaxhighlight>
		+	==Testsuite schematron to check payload==
		+	Testsuite schematron can be used to check whether message payload conforms to a specific testcase.
		+	See: [[Specifying_Tests_with_DECOR]]

@@ Line 99: / Line 99: @@
 The following variables are used in message templates.
-Note: the way to format xs:dayTimeDuration and picture-strings are part of the W3C standards. See: [http://www.w3.org/TR/xmlschema-2/#duration duration] and [http://www.w3.org/TR/xslt20/#date-picture-string date-picture-string] ([http://www.w3.org/TR/xslt20/#date-time-examples date-time-exmaples]).
+Note: the way to format xs:dayTimeDuration and picture-strings are part of the W3C standards. See: [http://www.w3.org/TR/xmlschema-2/#duration duration] and [http://www.w3.org/TR/xslt20/#date-picture-string date-picture-string] ([http://www.w3.org/TR/xslt20/#date-time-examples date-time-examples]).
 ===Variables typically used in message payload===

@@ Line 99: / Line 99: @@
 The following variables are used in message templates.
-Note: the way to format xs:dayTimeDuration and picture-strings are part of the W3C standards. See: [http://www.w3.org/TR/xmlschema-2/#duration duration] and [http://www.w3.org/TR/xslt20/#date-picture-string date-picture-string].
+Note: the way to format xs:dayTimeDuration and picture-strings are part of the W3C standards. See: [http://www.w3.org/TR/xmlschema-2/#duration duration] and [http://www.w3.org/TR/xslt20/#date-picture-string date-picture-string] ([http://www.w3.org/TR/xslt20/#date-time-examples date-time-exmaples]).
 ===Variables typically used in message payload===

@@ Line 111: / Line 111: @@
 </syntaxhighlight>
 <syntaxhighlight lang="xml" heading="In an example fragment" enclose="div">
-<author><time value="{format-date(current-date(),'[Y0001][M01][D01]')}"/>
+<author>
 </syntaxhighlight>
@@ Line 123: / Line 125: @@
 </syntaxhighlight>
 <syntaxhighlight lang="xml" heading="In an example fragment" enclose="div">
-<phase><center value="{format-date(current-date()-xs:dayTimeDuration('P31D'),'[Y0001][M01][D01]')}"/>
+<phase>
 </syntaxhighlight>
 With time appended (hardcoded in the template as a fixed time):
 <syntaxhighlight lang="xml" heading="In an example fragment" enclose="div">
-<phase><center value="{format-date(current-date()-xs:dayTimeDuration('P31D'),'[Y0001][M01][D01]')}0800"/>
+<phase>
 </syntaxhighlight>
@@ Line 138: / Line 143: @@
 </syntaxhighlight>
 <syntaxhighlight lang="xml" heading="In an example fragment" enclose="div">
-<queryAck><queryId extension="{$message/hl7:ControlActProcess/hl7:queryByParameter/hl7:queryId/@extension}" root="{$message/hl7:ControlActProcess/hl7:queryByParameter/hl7:queryId/@root}"/>
+<queryAck>
 </syntaxhighlight>
@@ Line 149: / Line 156: @@
 </syntaxhighlight>
 <syntaxhighlight lang="xml" heading="In an example fragment" enclose="div">
-<queryAck><queryId extension="{$message/hl7:ControlActProcess/hl7:queryByParameter/hl7:queryId/@extension}" root="{$message/hl7:ControlActProcess/hl7:queryByParameter/hl7:queryId/@root}"/>
+<queryAck>
 </syntaxhighlight>

@@ Line 97: / Line 97: @@
 == Using variables in templates ==
-The following variables are used in message templates:
+The following variables are used in message templates.
 ===Variables typically used in message payload===
 See also [[XIS_maintenance#Variables_typically_used_in_message_wrappers_for_reponse_templates|Variables typically used in message wrappers for reponse templates]] for elements such as id, creationTime, targetMessage.

@@ Line 64: / Line 64: @@
 When the XIS-server should receive interactions (not through upload), response templates should be present in /hl7/<HL7 material set>/message-templates
 Typically they will contain the response in XML which (based on the WSDL) should be returned to the remote application as a reply.
-See also the next sections which describe the variables which can be used in these templates.
+See also the next sections which describe the variables that can be used in these templates.
 Here is an example for an HL7-ack: