This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Artifact Domain Artifact Definition"
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
As used here, a domain is definition #3, as a qualification of definition #1. | As used here, a domain is definition #3, as a qualification of definition #1. | ||
− | |||
== SAIF Matrix Location == | == SAIF Matrix Location == |
Revision as of 15:16, 15 April 2011
Contents
- 1 Artifact Domain - initial
- 1.1 Definition and Purpose
- 1.2 SAIF Matrix Location
- 1.3 Audience
- 1.4 Applicability
- 1.5 Requirements, Relationships and Content
- 1.6 Artifact Technology
- 1.7 Content Constraints
- 1.8 Content Guidelines
- 1.9 Publishing Representation(s)
- 1.10 Publishing Constraints
- 1.11 Tooling Considerations
- 1.12 Development Process Considerations
- 1.13 Governance Process Considerations
- 1.14 Issues
Artifact Domain - initial
Definition and Purpose
Groups all of the artifacts defined by a particular HL7 functional 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.
- A particular area of interest. For example, the domain for HL7 is healthcare.
As used here, a domain is definition #3, as a qualification of definition #1.
SAIF Matrix Location
Row(s)
- Conceptual (CIM)
- Logical (PIM)
- Implementable (PSM)
Column(s)
- Enterprise/Business
- Information
- Computational
- Engineering
Audience
Health Care Community Audiences:
- General public
- Health care practitioners
- Health system administrators
- Health care policy makers
Health Care Information Technology (IT) Audiences:
- System designers and architects
- System purchasers
- Programmers/implementers
- System vendor management
Applicability
Text
Rationale: More text
Requirements, Relationships and Content
- Some requirement
- RationaleSome reason
- Some other requirement
- RationaleSome other reason
Relationships and traceability
- Some relationship
- Rationale: Reason for relationship
- Some other relationship
- Rationale: Reason for other relationship
Artifact types that may or must relate to this artifact types:
- Many-related Artifact Type
- Another Many-related Artifact Type
Content
- Content element name - Brief Description
- Another content element name - Brief Description
- Sub-element name - Brief Description
- Another content element name - Brief Description
Artifact Technology
Text here
Rationale
- Some reason
- Some other reason
Alternatives
Some technology
- Some pro or con
- Some other pro or con
Content Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Content Guidelines
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Publishing Representation(s)
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Publishing Constraints
- Some rule
- Rationale: Some reason
- Some other rule
- Rationale: Some other reason
Tooling Considerations
- Nice-to-have|Required: Some feature
- Rationale: Some rationale
- Nice-to-have|Required: Some other feature
- Rationale: Some other rationale
Development Process Considerations
- Some text
- Rationale: Some rationale
- Some other text
- Rationale: Some other rationale
Governance Process Considerations
- Governance Process name - Some process description
- Rationale: Some rationale
- Another Governance Process name - Process description
- Rationale: Some other rationale
Issues
- Some issue
- Some other issue