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

Difference between revisions of "Information Model Design Patterns"

From HL7Wiki
Jump to navigation Jump to search
Line 9: Line 9:
 
* Committee ballot decisions with respect to design patterns can be appealed to MnM. Final decision rests with TSC chair.
 
* Committee ballot decisions with respect to design patterns can be appealed to MnM. Final decision rests with TSC chair.
  
 +
== What is a design pattern? ==
 +
 +
A pattern provides guidance for a specific aspect of how to use the RIM to solve particular problems. The pattern is documented with example models, but these are not intended to be models from which working models are derived.
 +
 +
More substantial domain models such as Clinical Statement are sometimes described as design patterns, but are not included in this category.
  
 
== Enforced Templates ==
 
== Enforced Templates ==

Revision as of 13:58, 17 May 2011

Design Patterns for RIM Models

This page documents a series of design patterns that provide guidance for modelers producing RIM-based information models for HL7 publications.

  • All RIM modellers should be aware of design patterns.
  • Design patterns are subject to harmonization.
  • Checking for the correct use of patterns is part of full ballot quality criteria checking.
  • Balloters are welcome to comment in ballot about whether patterns are followed.
  • Committee ballot decisions with respect to design patterns can be appealed to MnM. Final decision rests with TSC chair.

What is a design pattern?

A pattern provides guidance for a specific aspect of how to use the RIM to solve particular problems. The pattern is documented with example models, but these are not intended to be models from which working models are derived.

More substantial domain models such as Clinical Statement are sometimes described as design patterns, but are not included in this category.

Enforced Templates

Templates Under Development


Template

These sections should be found in the documentation of each pattern:

  • what is the pattern?
  • why is it defined?
  • when is it appropriate? (and in what design paradigm?)
    • when must/should it be used?
    • when must/should it not be used?
  • where has it been used (example)?
  • where has it not been used (example)?
  • who maintains the pattern?
  • other variations