View source for Domain Information Model Artifact Definition

[[Category:SAIF Artifact Definition]]
[[:Category:SAIF Artifact Definition|Return to Artifact List]]

=Domain Information Model=
<!-- Artifact names should be descriptive and short.  They may change as we further refine the methodology -->
== Definition and Purpose ==
<!-- At a high level, what is this artifact and why is it needed?  Should ideally be only a few sentences -->
A Domain Information Model (DIM) represents the information content required to support a particular {#Domain|domain] within HL7. A DIM will commonly represent all of the information content that may required to be communicated in order to provide interoperability for the host domain, and will, therefore, be the source for all "derived" information models that are required to support HL7 interoperability specifications in that domain. 
=====Domain=====
From the V3 Glossary:
:Core Glossary:
:#A particular area of interest. For example, the domain for HL7 is healthcare.
:#:
:#The set of possible values of a data type , attribute, or data type component. See also vocabulary domain .
:#:
:#A special interest group within HL7, such as Pharmacy, Laboratory, or Patient Administration.

As used here, a domain is definition #3, as a qualification of definition #1.
== SAIF Matrix Location ==

<!-- Where does this artifact fit into the SAIF matrix?  Delete those rows and columns that do not apply and provide qualification if appropriate -->
'''Row(s)'''
* Logical (PIM)

'''Column(s)'''
* Information

== Audience ==

Health Care Information Technology (IT) Audiences:
*System designers and architects
*System vendor management

== Applicability ==
<!-- Under what circumstances does this artifact type need to be created?  Are there circumstances where this artifact should not exist?  Why? -->
A DIM MUST exist before a project within the domain being represented can create derived models to meet the projects needs.  Thus there will be at least one DIM for each domain of interest within HL7. 
:<i>Rationale</i>: As part of the HL7 model-based methodology, a DIM must be "derived from" the RIM, and any Serializable Information Model (SIM) defined by a domain MUST be "derived from" that domain's DIM. 

== Requirements, Relationships and Content ==
<!-- What are the needs that this particular artifact was created to satisfy and why are those needs important.   (Should not be more than 10-15.) -->
{{Template:SAIF Generic IM Requirements}}
=== Relationships and traceability ===
<!-- What are the other artifacts to which this artifact must or may be required to relate?  (Express those relationships that are "many-to-one" - that is where many of this artifact type will usually relate to one of the other artifact type.) How do they relate?  Why is the relationship important? 

Follow with a bullet list of artifacts that may or must relate to this artifact, where many of the listed artifact type will relate to one of this artifact type.  
 -->
*All of the contents of this Domain Information Model MUST be '''derived from''' an artifact whose type is either the Reference Information Model or another Domain Information Model.  Derivation rules are discussed under [[#Content Constraints|Content Constraints]] below.
**<i>Rationale</i> These derivation relationships that ultimately derive from the RIM are at the heart of HL7's V3 model-driven methodology and architecture.
{{Template:SAIF Generic IM Relationships}}

<b>Artifact types that may or must relate to this artifact types:</b>
* [[Conceptual Information Model Artifact Definition|Conceptual Information Model ]]
* [[Serializable Information Model Artifact Definition|Serializable Information Model]]

=== Content ===
<!-- What elements or components are required to be part of this artifact, and what is their hierarchical structure?  How?  Why is the content important? (These can be expresses as a hierarchical set of content element names, with a brief phrase to describe each.) -->
{{Template:SAIF Generic IM Content }}

== Artifact Technology ==
<!-- What technological/standard solution has been selected for use in creating this artifact and why? -->
{{Template:SAIF Generic IM Technology}}

== Content Constraints ==
<!-- What are the formal rules about how the artifact can be constructed, including any extensions and constraints for the selected technology as well as the rationale for those rules.  These are rules that can reasonably be enforced or validated by tools. -->
{{Template:SAIF Generic IM Constraints}}
== Content Guidelines ==
<!-- What are the informal guidelines about how the artifact content.  I.e. What constitutes good practice?  These guidelines should be used in the evaluation of artifact instances but generally can't be enforced or validated by tools. -->
{{Template:SAIF Generic IM Content Guidelines}}

== Publishing Representation(s) ==
<!-- How will this artifact be shared and published as part of specifications? -->
{{Template:SAIF Generic IM Publishing Representation}}

== Publishing Constraints ==
<!-- What are the constraints imposed by the publishing process on how artifacts are constructed and submitted to HL7and what are the reasons behind such constraints? -->

== Tooling Considerations ==
<!-- What tooling features are required or "nice to have" to allow successful development, publication or other use of the artifact? -->
{{Template:SAIF Generic IM Tooling}}

== Development Process Considerations ==
<!-- This section is optional.  It identifies thoughts or guidance around how the artifact will be used.  This may include development process, guidance on how many of this type of artifact are likely to exist within a domain or topic, etc. -->
{{Template:SAIF Generic IM Development}}

== Governance Process Considerations ==
<!-- This section is optional.  It identifies anticipated or existing governance processes that control or impact the development and adoption of this type of artifact.  -->

== Issues ==


<!-- This section is optional. It identifies any outstanding issues (methodology or otherwise) that need to be resolved/answered as part of the guidelines -->

* Some issue
* Some other issue