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

FHIR Governance Precepts

From HL7Wiki
Revision as of 12:03, 22 April 2014 by Gwbeeler (talk | contribs)
Jump to navigation Jump to search

Category:FHIR Discussion

Precept Table

' ' Goals Constraints Conformity
Precept ID Short Name Objectives Policies Standards
Pr-00 HL7 (TSC and GOM) Rules

New Addition: In all matters, the precepts and rules established in the HL7 Governance and Operations model apply to the governance of FHIR. Precepts listed here extend or supplement the GOM. The FHIR Governance Board is established by, and reports to the HL7 Technical Steering Committee.

Humbly suggest that the "Policy" for all of these, presuming a decent definition of the objective is simply:
"Make it happen!"
Similarly, for the most part, standards can be delegated to either the methodology or the specification itself.
Pr-01 FHIR Adoption Scope

Initial market segmentation and value proposition. Identification of scope of Resources for initial DSTU. Criteria for expanding scope including discovery of requirements, PL Vitality Assessment.

Summarize the KNOWN CURRENT serious implementations - we cannot control it, but we should document it. Resources are what they are.

Humbly suggest that the "Policy" for all of these, presuming a decent definition of the objective is simply:
"Make it happen!"
Similarly, for the most part, standards can be delegated to either the methodology or the specification itself.
Pr-02 FHIR Org Maturity Model

Definition of stages of organizational maturity for the design, development, and deployment of FHIR.

Seems a futile exercise, in an organization where its maturity governs what it does rather than the other way around. Might be a great sociology exercise, but will it help us find people resources, much less mature ones?

Pr-03 FHIR Resourcing Model

Framework for identifying, assigning, and managing Resources necessary to product FHIR products.

See comment above

Pr-04 HL7 Business Dictionary

Organizational repository for "terms of the art" that is used and contributed to by the FHIR team

Suggest this is a concise recitation definitions of resources, extensions, profiles, mappings, and referfence implementations.

Pr-05 Resource Meta-Data Standards

Standards for the identification and description of Resources that ensure uniqueness, discover-ability, effective normalization, and compositional coherence of Resources.

Sounds like something Beeler proposed. Need to keep it real. How well is current meta-data doing with these principles?

Pr-06 Resource Ontology

Big words. What's it mean?

Pr-07 Resource Taxonomy Taxonomy for Resources
Pr-08 FHIR Inventory Scope Definition
Pr-09 Candidate Resource Naming Taxonomy and Standards for Resource Naming
Precept: "Methodology needs to provide this."
Pr-10 Resource Normalization Resources are context neutral, composable, unique
Preceding says it all."
Pr-11 Resource Versioning Standards for versioning of Resources
Precept: "Methodology needs to provide this."
Pr-12 Resource Design Methodologies and standards for resource design
Precept: "Methodology needs to provide this."
Pr-13 Resource Description Methodology and standards for metadata and requirements traceability
Precept: "Methodology needs to provide this."
Pr-14 Resource Template Design pattern for building a Resource definition
Precept: "Methodology needs to provide this."
Pr-15 Profile Template Design pattern for profiling and assembling composite Resources
Precept: "Methodology needs to provide this."
Pr-16 Requirements Traceability
Pr-17 Implementation Guide Framework, methodology and standards for developing and maintaining a FHIR implementation guide
Pr-18 Internal Publication Methodology, standards, and processes for publishing of FHIR products internally for review and balloting
Pr-19 Balloting Methodology, standards, and processes for balloting of FHIR products
Pr-20 External Publication Methodology, standards, and processes for publishing of FHIR products as standards for use
Pr-21 Resource Usage Tracking Methodology and processes for tracking Resource utilization by HL7 customers
Pr-22 Resource Vitality Triggers Metrics and methodology for assessing the vitality of Resources and triggering
Pr-23 Resource Registry Repository for all Resources, planned, in development, ballot type, and published. Includes custodian identity and contact information, versioning history, "where referenced", effective date, retirement date, etc as defined in metadata definition.
Pr-24 Resource Versioning Strategy

Conformity Metrics

Metric ID Short Name Type Description Precepts applied to

Governance Processes

Process Id Short Name Governance Point Type Description Tools Methodology

People

Role Role Assigned To: Product Specific Responsibilities Required Skills Required Subject Matter Expertise
Administrator - Resource
Analyst - Business
Analyst - Resource
Architect - Resource
Archivist
Ballot Lead
Custodian
Design Standards Custodian
Developer
Enterprise Architect
Governance Board
Governance Specialist
Management Group
Methodology Facilitator
Policy Custodian
Product Registry Custodian
Project Lead
Proponent
Publisher
Quality Assurance Specialist
Security Specialist
Technical Communications Specialist
Template Custodian

Reference Section

Reference Values ' Description
Core Processes
Conformity Assessment
Education
Escalation
Vitality Assessment
Conformity Metrics
Cost Within HL7 we need a definition of "Cost" or other proxies for measuring the relative cost to the organization of certain choices. In some cases, cost includes actual budget consumption for tooling and other issues, in other cases the cost might be scarcity of time, reduced or unavailable capacity, etc.
Threshold
Standards-based
Vitality Metrics
Conformity
Cost
Performance
Vitality Triggers
IT Shift
Metrics
Organizational Shifts
Periodic
Strategic Business Adjustment
Strategic IT Adjustment
PL Governance Points
Balloting and Ballot Resolution
Conformity Assessment
Line Planning
PL Vitality Assessment
Production
Publication
Requirements Definition
Governance Tooling
QA Tool
Registry
Repository
Skills
Publication management
Modeling
Technical Editing
Quality Assurance
Role
Administrator - Resource
Analyst - Business Responsible for the gathering of requirements, the decomposition of those requirements into discrete components that can be solved for, and the provision of conformance criteria that will allow validation that requirements have been met.
Analyst - Resource Responsible for identifying the taxonomy of Resources, their appropriate forms, as well as ensuring Resources are fit-for-purpose. Defines conformance criteria that will allow validation that a resource is well-formed and properly normalized.
Architect - Resource Provides the design framework within which Resources are described and and developed. An expert in the structure of Resources and their recomposition.
Archivist Responsible for collecting, editing, and assembling documentation to support the design, development, balloting and publication of products. Also responsible for posting agendas, capturing, organizing, and posting meeting minutes, and monitoring processes and metrics related to continuity of work.
Ballot Lead Responsible for ensuring ballot content is complete (relative to the nature of the particular ballot), timely, and transmitted for pre-ballot publishing. Responsible for reconciliation of ballot responses, assignment of related revisions, and communication of the reconciliaton to ballot commenters.
Custodian Responsible for the management and governance of one or more Resources. This includes protecting the integrity of the Resource content as well as its associated functional boundary. Ensures that Resources are appropriately deployed and maintained, their usage is appropriate and monitored, that they are discoverable, versioning is mangaged, and if necessary that they are appropriately and effectively retired.
Design Standards Custodian Ensures that design standards are kept in alignment and used wherever appropriate. Responsible for the evolution of design standards as well as their enforcement.
Developer A standards designer / developer proficient in the tools, methodologies, and product standards required to build Resources.
Enterprise Architect Assists in Product Line planning from the perspective of organizations that will consume the products. Contributes to enterprise design standards. Ensures that agnostic Resources are properly positioned. Helps define Resource inventory blueprint. Involved in Resource planning, inventory analysis, Resource modeling.
Governance Board Ensure the organizational asset is effectively and appropriately governed to achieve its strategic goals and objectives while fitting within the larger goals and objectives of the organization.
Governance Specialist
Management Group
Methodology Facilitator
Policy Custodian
Product Registry Custodian
Project Lead
Proponent
Publisher
Quality Assurance Specialist
Security Specialist
Technical Communications Specialist
Template Custodian
Subject Matter Expertise
Anatomic Pathology
Anesthesia
Arden Syntax
Attachments
CCOW
Child Health
Clinical Decision Support
Clinical Genomics
Clinical Quality Information
Clinical Research
Clinical Statement
Community Based Collaborative Care
Conformance & Testing
Education
Electronic Health Records
Electronic Services
Emergency Care
Financial Management
Governance and Operations
Health Care Devices
HL7 Policy
Imaging Integration
Infrastructure and Messaging
Marketing
Mobile Health
Modeling and Methodology
Orders and Observations
Organizational Relations
Patient Administration
Patient Care
Patient Safety
Pharmacy
Process Improvement
Project Services
Public Health and Emergency Response
Publishing
RIM Based Application Architecture
Security
Services Oriented Architecture
Structured Documents
Templates
Tooling
Vocabulary