This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Interoperability Paradigm"
Jump to navigation
Jump to search
m (Created page with "'''Interoperability paradigm (IP)''' Interoperability paradigm (IP) is a set of fundamental principles that establishes the ground rules for the different approaches to [http://...") |
Rene spronk (talk | contribs) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 6: | Line 6: | ||
#How templates are to be used. | #How templates are to be used. | ||
#In what form it is exchanged. The [http://www.hl7.org| HL7] interoperability paradigms are [[Message-SAIF| messages]], [[Document-SAIF|documents]], and [[Services-SAIF | services]]: | #In what form it is exchanged. The [http://www.hl7.org| HL7] interoperability paradigms are [[Message-SAIF| messages]], [[Document-SAIF|documents]], and [[Services-SAIF | services]]: | ||
− | #[[Message-SAIF| Messages]] - The transmission of semantically rigorous, contextually self-contained information structures according to pre-determined trigger conditions along well known interaction paths. | + | ##[[Message-SAIF| Messages]] - The transmission of semantically rigorous, contextually self-contained information structures according to pre-determined trigger conditions along well known interaction paths. |
− | # [[Document-SAIF|Documents]] - A business-oriented container that becomes the focal class that may be exposed through a service interface (for administration, querying, and manipulation), or transmitted via a [[Message-SAIF| message]]. | + | ##[[Document-SAIF|Documents]] - A business-oriented container that becomes the focal class that may be exposed through a service interface (for administration, querying, and manipulation), or transmitted via a [[Message-SAIF| message]]. |
− | # [[Services-SAIF | Services]] - A structured behavioral interface being exposed that provides fine-grained control of some capability, often a focal class, such as an order or a transactional process. These capabilities are, in turn, invoked through smaller, function-oriented [[Message-SAIF |message]] structures that retain the semantic rigor of [http://www.hl7.org | + | ##[[Services-SAIF | Services]] - A structured behavioral interface being exposed that provides fine-grained control of some capability, often a focal class, such as an order or a transactional process. These capabilities are, in turn, invoked through smaller, function-oriented [[Message-SAIF |message]] structures that retain the semantic rigor of [http://www.hl7.org HL7] models without realizing the entirety of the semantic in the [[Message-SAIF | message]] structure. |
− | [[Category:SAIF Glossary]] | + | [[Category:SAIF Glossary]] |
− | |||
− |
Latest revision as of 08:26, 22 April 2011
Interoperability paradigm (IP)
Interoperability paradigm (IP) is a set of fundamental principles that establishes the ground rules for the different approaches to HL7 V3-based information exchange. The IP must answer
- When information is exchanged.
- How application implementation details are specified.
- How templates are to be used.
- In what form it is exchanged. The HL7 interoperability paradigms are messages, documents, and services:
- Messages - The transmission of semantically rigorous, contextually self-contained information structures according to pre-determined trigger conditions along well known interaction paths.
- Documents - A business-oriented container that becomes the focal class that may be exposed through a service interface (for administration, querying, and manipulation), or transmitted via a message.
- Services - A structured behavioral interface being exposed that provides fine-grained control of some capability, often a focal class, such as an order or a transactional process. These capabilities are, in turn, invoked through smaller, function-oriented message structures that retain the semantic rigor of HL7 models without realizing the entirety of the semantic in the message structure.