This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Conformance SIG"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) (new section related to proposal 908) |
||
| Line 4: | Line 4: | ||
One of the key HL7 v3 conformance artefacts is the [[Application Role]], a core element of a [[Conformance Claim]]. | One of the key HL7 v3 conformance artefacts is the [[Application Role]], a core element of a [[Conformance Claim]]. | ||
| + | |||
| + | During the Phoenix (January 2006) WGM the Conformance SIG (and MnM/INM) had a look at the proposed Feature Discovery Interactiona s described in the | ||
| + | [http://www.hl7.org/Library/Committees/cq/20040827%5FHL7%5Fprop%5F908%2Edoc Ping and Feature Discovery proposal document]. The Conformance SIG expressed it would be useful to have such an interaction, and approved a motion to work with INM to progress the proposal in San Antonio. It was however unclear if a new HL7 interaction should be developed, or whether we should re-use an existing industry standard. | ||
Revision as of 12:55, 22 January 2006
The Conformance Special Interest Group is working on creating conformance criteria for HL7 2.x and V3.
Here we should add documentation and FAQs.
One of the key HL7 v3 conformance artefacts is the Application Role, a core element of a Conformance Claim.
During the Phoenix (January 2006) WGM the Conformance SIG (and MnM/INM) had a look at the proposed Feature Discovery Interactiona s described in the Ping and Feature Discovery proposal document. The Conformance SIG expressed it would be useful to have such an interaction, and approved a motion to work with INM to progress the proposal in San Antonio. It was however unclear if a new HL7 interaction should be developed, or whether we should re-use an existing industry standard.
