This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Conformance Statement"

From HL7Wiki
Jump to navigation Jump to search
 
m
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
Message Conformance is just one (of the important) elements in a conformance claim. A conformance claim describes in a 5 page overview:
+
'''Conformance Statement'''
 +
*''Functional statement:'' Support for interactions linked to roles (as defined in a [[Conformance Profile]]). Interactions are based on static modeling artifacts; these are constrained as well in a conformance profile.
 +
**Could be expressed as the Identifier (an OID) of the (set of) MWB/MIF files, and the highlights of these files (here: what interactions are supported). The MWB (in v2) or MIF-based tools (in v3) can be used to test this conformance aspect.
 +
*''Technical statement:'' support for a specific ITS (e.g. XML ITS); batch- or sequence number protocol support; support for the Queue, Immediate and or the Deferred responseMode.
  
-The role/functionality of the application (0.5 of a page)
+
See also [[Conformance_claim|conformance claim]]
-The version (Normative Edition) of HL7 it supports
 
-What other conformance documents or profiles do they claim conformance to (an HL7 profile, an IHE profile, a vendor profile, an HL7 affiliate profile, etc.)
 
-The transport protocols it supports, does it support the HL7 defined Transport protocols and if so, how. What is the implementation profile for the transport ?
 
-What interactions does this application send/receive ?
 
-Does the application support the Queue, Immediate and or the Deferred responseMode, and if so for what interactions ? What accept ack/nak model is being used ?
 
-Have they extended the standard, if so: where, and why ?
 
  
A conformance claim will only contain the OID of the (set of) MWB/MIF files, and the highlights of these files (here: what interactions are supported).
+
[[Category:SAIF Glossary]]
 
 
IMHO the purpose of a conformance statement/claim is that one gets a quick and pretty complete overview of all issues that are important when trying to decide (at a high level) "will this application X be able to communicate with application Y".
 
 
 
If the answer is Yes, then one starts a testing process using all kinds of tools to test the syntactic/semantic details. This is where tools like the MWB come in.
 

Latest revision as of 18:15, 10 November 2011

Conformance Statement

  • Functional statement: Support for interactions linked to roles (as defined in a Conformance Profile). Interactions are based on static modeling artifacts; these are constrained as well in a conformance profile.
    • Could be expressed as the Identifier (an OID) of the (set of) MWB/MIF files, and the highlights of these files (here: what interactions are supported). The MWB (in v2) or MIF-based tools (in v3) can be used to test this conformance aspect.
  • Technical statement: support for a specific ITS (e.g. XML ITS); batch- or sequence number protocol support; support for the Queue, Immediate and or the Deferred responseMode.

See also conformance claim