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 1: | Line 1: | ||
| − | + | A '''Conformance Claim''' is a set of conformance statements: Functional and Technical. | |
| + | *''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. | ||
| + | Next to the above statements, a conformance claim contains 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". | ||
*The role/functionality of the application (0.5 of a page) | *The role/functionality of the application (0.5 of a page) | ||
| − | *The version (Normative Edition) of HL7 it supports | + | *The version (or: Normative Edition) of HL7 it supports |
| − | *What other conformance documents or profiles | + | *What other conformance documents or profiles does the application 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 ? | *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 ? | ||
| − | + | *Does the application use extensions with regards to the standard, if so: where, and why ? | |
| − | *Does the application | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Related== | ==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). | *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 12:42, 3 November 2008
A Conformance Claim is a set of conformance statements: Functional and Technical.
- 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.
Next to the above statements, a conformance claim contains 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".
- The role/functionality of the application (0.5 of a page)
- The version (or: Normative Edition) of HL7 it supports
- What other conformance documents or profiles does the application 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 ?
- Does the application use extensions with regards to the standard, if so: where, and why ?
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).
