This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Information Model Design Patterns"
Jump to navigation
Jump to search
| Line 30: | Line 30: | ||
* where has it been used (example)? | * where has it been used (example)? | ||
* where has it not been used (example)? | * where has it not been used (example)? | ||
| − | * who | + | * who maintains the pattern? |
* other variations | * other variations | ||
Revision as of 13:56, 17 May 2011
Contents
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.
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
