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

Difference between revisions of "Template:SAIF Generic IM Requirements"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
<noinclude><span style="color:#0000FF">Generic requirements for SAIF Information models.<br/>
 
<noinclude><span style="color:#0000FF">Generic requirements for SAIF Information models.<br/>
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Only the content appearing below in <span style="color:#000000">black font</span> will appear in the inclusion.</b><br/>  
 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>Only the content appearing below in <span style="color:#000000">black font</span> will appear in the inclusion.</b><br/>  
These elements are intended to appear under the following section:</span>
+
These elements are intended to appear under the following section:
 +
 
 +
[[:Category:SAIF Artifact Definition|goto to SAIF artifact definitions]]</span>
 
==<span style="color:#0000FF"> Requirements, Relationships and Content </span>==
 
==<span style="color:#0000FF"> Requirements, Relationships and Content </span>==
 
</noinclude>
 
</noinclude>

Revision as of 18:00, 10 April 2011

Generic requirements for SAIF Information models.
         Only the content appearing below in black font will appear in the inclusion.
These elements are intended to appear under the following section:

goto to SAIF artifact definitions

Requirements, Relationships and Content

  1. Include the set of classes, attributes and associations from the parent (derived from) model that represent the information needed to support interoperability in the domain or project that this model will support.
    1. RationaleDerived Models must use the RIM-derived model content needed to support the interoperability project in question.
  2. Maintain a degree of abstraction appropriate to the level of the model, remembering that models derived from this model can be more specific.
    1. Rationale Large models with myriad classes may obscure the core patterns and concepts that need to be represented in a particular DIM, SIM or other model.