This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Conformance Statement"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 14: | Line 14: | ||
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. | 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. | ||
| + | |||
| + | ==Related== | ||
| + | *An [[Conformance Profile]] is a is a ''machine testable'' specification of all kinds of conformance issues related to '''one single interaction'''. This profile is also known (in v2) as a '''Message Profile'''. The Conformance Statement may reference (a set of) Conformance Profile(s). | ||
Revision as of 08:57, 3 November 2008
Message Conformance is just one (of the important) elements in a conformance claim. A conformance claim describes in a 5 page overview:
- The role/functionality of the application (0.5 of a page)
- 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).
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.
Related
- An Conformance Profile is a is a machine testable specification of all kinds of conformance issues related to one single interaction. This profile is also known (in v2) as a Message Profile. The Conformance Statement may reference (a set of) Conformance Profile(s).
