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

Difference between revisions of "Template"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
'''Glossary Definition:''' a HL7 '''Template''' is a registered set of constraints on a balloted HL7 [[Static Model]]. The [[TemplateId]] contains the unique identification of a template.
 
'''Glossary Definition:''' a HL7 '''Template''' is a registered set of constraints on a balloted HL7 [[Static Model]]. The [[TemplateId]] contains the unique identification of a template.
 +
 +
==FAQ==
 +
*What's the difference between a [[Template]] and a [[CMET]]?
 +
**The short answer:
 +
***A [[CMET]] is a model/schema, used as a building block in other models/schemas.
 +
***A template is a model/schema, used to constrain a more general model/schema.
 +
**Fundamentally, we have serialized static models.  Those static models can be used in different ways - as payloads, as the bindings for one or more CMETs, or as templates.  A given static model can be used for any or all of these purposes.
 +
***When used as a CMET it becomes an integrated part of a message model, plugged in. There is one message model made up of components and you can make one message schema from it that validates all your constraints.
 +
***When used as a template, it doesn't become part of the message model itself (and isn't present in the message schema). It is an extra model in its own right that can be used to describe additional things not in the base message model. Use as templates is determined at runtime by the sender.

Revision as of 12:14, 29 April 2007

Glossary Definition: a HL7 Template is a registered set of constraints on a balloted HL7 Static Model. The TemplateId contains the unique identification of a template.

FAQ

  • What's the difference between a Template and a CMET?
    • The short answer:
      • A CMET is a model/schema, used as a building block in other models/schemas.
      • A template is a model/schema, used to constrain a more general model/schema.
    • Fundamentally, we have serialized static models. Those static models can be used in different ways - as payloads, as the bindings for one or more CMETs, or as templates. A given static model can be used for any or all of these purposes.
      • When used as a CMET it becomes an integrated part of a message model, plugged in. There is one message model made up of components and you can make one message schema from it that validates all your constraints.
      • When used as a template, it doesn't become part of the message model itself (and isn't present in the message schema). It is an extra model in its own right that can be used to describe additional things not in the base message model. Use as templates is determined at runtime by the sender.