This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Core Properties of V3 Models"

From HL7Wiki
Jump to navigation Jump to search
 
(164 intermediate revisions by 6 users not shown)
Line 1: Line 1:
=Core Properties of V3 Models=
+
= Posting on Wiki WITHDRAWN in Its Entirety =
 +
This document was originally posted for dicussion prior to the first release of the COre Principles document.  Subsequently, this document has gone through four (soon to be five) ballots.  The content on this Wiki page has been entirely superseded and has, therefore been removed.
  
 +
The Ballot content [http://www.hl7.org/v3ballot/html/infrastructure/coreprinciples/v3modelcoreprinciples.html may be available here].
  
= Preface =
+
[[User:Gwbeeler|GWBeeler]] 14:58, 4 April 2011 (UTC)
 
 
== Notes to Readers ==
 
 
 
This is the first release of this document. It is intended to
 
provide important background information for implementors
 
trying to implement V3 Static Models, whether they are found
 
in Messages, Documents, or Service Payloads.
 
 
 
== Acknowledgements ==
 
 
 
Authors:
 
* George W Beeler
 
* Grahame Grieve
 
 
 
= Introduction and Scope =
 
 
 
* a description of the Document at a minimum sufficient for a person unfamiliar with the work to understand the document’s business, scope and relationship with HL7.
 
 
 
* the need for a Specification.
 
 
 
= V3 Static Models: Overview =
 
 
 
All V3 Static Models are comprised of [[#RIM]] classes linked by associations.
 
The classes have attributes which are assigned [[#datatypes]]. Some attributes
 
are associated with controlled [[#vocabularies]] which provide clearly defined
 
semantic meaning to the static models.
 
 
 
== RIM ==
 
 
 
The [[RIM]] defines all the classes that are used in static models. The classes
 
are standard classes in the UML sense, and have associations and attributes
 
as defined in the RIM models.
 
 
 
== Datatypes ==
 
 
 
The datatypes define the types that may be used for the attributes
 
of the RIM classes. The semantics of the types are defined in the 
 
[[abstract datatypes]], while the [[ITS datatypes] define an XML
 
implementation of the datatypes
 
 
 
== Vocabulary ==
 
 
 
comments about constraints
 
 
 
== Refinement, Constraint, and Localization ==
 
== Templates ==
 
 
 
Comments about classes, associations, attributes, datatypes and controlled vocabularies
 
 
 
= Key Concepts =
 
 
 
== Null Flavor ==
 
 
 
== Cardinality & Optionality ==
 
 
 
== Conformance ==
 
 
 
=== Testing Considerations ===
 
 
 
== Vocabulary Conformance ==
 
 
 
* domains
 
* coding strength
 
 
 
== Type Representation ==
 
 
 
**typing (typeId & flavorId & templates)
 
 
 
== Update control ==
 
 
 
== Referencing Acts ==
 
 
 
== Update Mode ==
 
 
 
*doco
 
**use cases
 
**data types
 
**classes
 
 
 
=introduction to how RIM & datatypes fit together=
 

Latest revision as of 15:00, 4 April 2011

Posting on Wiki WITHDRAWN in Its Entirety

This document was originally posted for dicussion prior to the first release of the COre Principles document. Subsequently, this document has gone through four (soon to be five) ballots. The content on this Wiki page has been entirely superseded and has, therefore been removed.

The Ballot content may be available here.

GWBeeler 14:58, 4 April 2011 (UTC)