(I have tried to send this several times. I hope this one takes). >From the GCPR perspective, we do not view HL7 and CORBAmed activities as incompatable (or competing). I have attached an informal document which we used within the GCPR to help identify concerns, deliverables, and get a handle on process and products which were needed to get the job done. This is the matrix to which Mary Kratz referred in her recent message. I'd like to note to those HL7 people who will be attending in San Diego that this will be presented at the Government SIG. Though I'm not sure when it is on the agenda, I believe it is during the Tuesday AM session. Based on the attached, the HL7 RIM was the primary starting point for the "Domain Context", and the CORBAmed services the primary point for the "Service Context". This matrix is still a work in progress, and we welcome input and comments on it [feel free to email to me directly]. I hope it helps to clarify roles, and encourage this list to use it as appropriate. - Ken Rob Cecil wrote: > Given Gunther's comments (12/28) regarding the incompatibility of HL7 > RIM and CORBAmed, how is this possible? > -- ********************************************************************** Rubin, Kenneth S. E-Mail : [EMAIL PROTECTED] EDS-D/SIDDOMS Phone : (703) 845-3827 5113 Leesburg Pike FAX : (703) 845-3899 Skyline 4 Suite 300 Falls Church, Virginia 22041 **********************************************************************Title: Government Reference Modeling Activity Breakout
GCPR “Generic” Government Reference Modeling Taxonomy Matrix v. 0.1
|
Specification |
Enterprise Viewpoint |
Information Viewpoint |
Computational Viewpoint |
Engineering Viewpoint |
Technology Viewpoint |
|
|
|
||||
|
Explanation
|
Purpose, scope, and policies |
Information and related processes, addressing info. reference and semantics |
Funct decomposition. Distribution partitioning. |
Distribution-oriented aspects of the system. |
Implementation specifics |
|
Domain Context
|
Used to describe scope, policy, and purpose for implement-ation, particularly those concerns which are not automated (e.g., inter and intra-organizational issues)
Sample Artifact(s): Scope Narrative, Statement of Objectives, “Concept of Operations”, etc. Graphics such as org. charts, etc. |
Representation of information domain (e.g., healthcare) and interrelationships within this business environment as pertaining to the scope defined within the enterprise viewpoint.
Sample Artifact(s): -UML Class, State Diagrams -Semantic models -Terminology models |
Domain triggers, relationships, use cases pertaining to the healthcare business domain.
Sample Artifact(s): -Scenarios -UML Use Case Diagrams -Use Case Templates |
UML, OCL models;
Terminology and Lexicon
Sample Artifact(s): -Modeling “binaries” -Terms/codesets -Text Deliverables |
Since the scope of the domain context is primarily content definition, there are no technology viewpoint constraints.
Sample Artifact(s): None |
|
Service Context
|
Component “services” required to support domain context specification. Can be considered to be a “reference design.” Will be influenced by identified implementation architecture.
Sample Artifact(s): -Narrative with supporting graphics. -Baselined requirement set -UML Use Case Diagrams |
Service definition, list, information requirements and parameters. Akin to CORBAmed services’ info models.
Sample Artifact(s): -UML Class Diagram -UML State Diagram -Semantic/Terminology Models |
Specifications at a low level of detail highlighting interaction between the services or subsystems
Sample Artifact(s): -UML Sequence Diagrams -UML Collaboration Diagrams -Reference and Terminology Model Mappings
|
Means by which to forward Govt. interests to SDOs addressing inter-operability services.
Sample Artifact(s): -Interface Descriptions (ISO IDL)
|
Basis on which the system architecture will be based (e.g., MOM, distributed objects, etc.)
Sample Artifact(s): -Description of Conceptual Architecture -Implementation Product Selection |
|
Implementation Context
|
Sample Artifact(s):
-Project Plan -System Requirements Specification |
Sample Artifact(s):
-Populated Lexicon, -Instantiated codesets
|
Sample Artifact(s):
-System Design -Database Design -Component Code |
Sample Artifact(s):
-Infrastructure deployment model |
Sample Artifact(s):
-Product installation and training |
GCPR “Generic” Taxonomy Matrix v0.1. Draft version for public comment. http://www.gcpr.gov
