TSC Approved: 2018-09-24_TSC_Call_Agenda
ARB recommendation:
When there is a new product family or methodology the TSC SHOULD follow the steps detailed in the BAM: Especially 1.1.12 the ‘TSC task force’ makes a recommendation as to whether the organization should proceed.
(Adapted from the HL7 Business Architecture Model, Release 1)
Product Definition and Approval
The first stage in the Standards Production Lifecycle is Product Definition and Approval. In this stage the organization assesses the opportunity and relative need for a new product or set of products and makes a decision whether to proceed to develop the standard. It is important to note that the trigger event for this stage should be:
- A new product Family - a collection of products that share common elements, methodologies, and tools as viewed from a design perspective.
- A new methodology,
- An existing product or set of capabilities that a proponent feels should be an HL7 standard.
The following list, not exhaustive, requires a concept review:
- Proposed new standards not based on existing HL7 standards.
- Implementation guides not based on existing HL7 standards.
- Content not historically in HL7 Scope.
- Content not considered in the healthcare domain.
- New methodologies.
1.1.8 Create Product Concept Proposal
The initial step in this stage is to document the proposal for new interoperability standards product(s). In this step, the product proponent develops a proposal that includes the product concept, the attributes of the product that make it different than existing HL7 products, and an initial assessment of what portion of the market would find value in this particular proposed HL7 interoperability product (or products). In addition, the proponent provides one or more concrete examples of what the product is and does.
Artifacts Created | Description | How Used |
---|---|---|
Product Concept Proposal | Documentation of the concept, it’s attributes and an intent to take a particular action which must receive the endorsement or approval by a governance body before proceeding. | For the initial evaluation by HL7 |
Initial Market Segmentation | To identify the target audience and help determine customer needs and the uniqueness of the proposed product concept. | To identify the target audience and help determine customer needs and the uniqueness of the proposed product concept. |
Concept Example | A specific instance of the concept constructed to show either typical or exceptional characteristics to assist a user to better understand the concept. | To promote consistency of understanding and reduce the cognitive burden for those new to the concept. |
Participation | Role | Assigned to |
---|---|---|
Author | Advocate | Product Proponent |
1.1.9. Review Product Concept Proposal
Once the product concept proposal is created, it is brought forward to the HL7 TSC for evaluation. Typically, the TSC will commission a task force of limited duration and scope to perform the assessment. Working with the proposal author, the HL7 Product Director, and a sponsoring work group the task force tests the validity of the project proponent’s concepts and assertions with members of the organization and other representatives of the interoperability community as they see fit.
Artifacts Created | Description | How Used |
---|---|---|
Aspiration Confirmation | Documentation verifying that the proponent’s product aspiration is sufficiently described and documented in the product proposal artifacts. | As a validation check to assert sufficiency of concept documentation. |
Proposal Assessment | Evaluation of the proposal for completeness, relevance, well-formedness and validity as a new product within HL7. | To document the outcomes of the product concept review and assert readiness for downstream submission and adjudication. |
Participation | Role | Assigned to |
---|---|---|
Author | Proponent | Individual |
Supervisor | Reviewer | Product Director |
Product Director | Reviewer | Individual |
Consultant | Reviewer | Organization |
Reviewer | Reviewer | TSC Task Force |
1.1.10. Concept Recommendation
Artifacts Created | Description | How Used |
---|---|---|
Concept Recommendation | Recommend the concept to the organization | Creates the final concept recommendation |
Participation | Role | Assigned to |
---|---|---|
Author | Problem Space Analyst | Individual |
1.1.11. Create Organizational Readiness Assessment
Artifacts Created | Role | How Used |
---|---|---|
Readiness Assessment | Evaluation of the organization and its ability, capacity and desire to develop the proposed product or methodology. | As a check point to ensure that HL7 is equipped to develop the product or methodology if the proposal is approved by governance bodies. If HL7 or related organizations are not ready, the HL7 Product Publishing Lifecycle does not proceed. |
Participation | Role | Assigned To |
---|---|---|
Interested Party | Proponent | Individual |
Reviewer | Product Director | Product Director |
Author | Problem Space Analyst | Individual |
Accountable group | Project leader | TSC |
Contributor | Consultant | Steering Division Chairs |
Contributor | Consultant | HQ |
SME | Methodologist | Appropriate Methodology Group(s) |
SME | Consultant | ARB Representative |
SME | Problem Space Analyst | Problem space analyst who is NOT the author,or associated with the concept.. |
1.1.12. Create Product Opportunity Recommendation
Documentation of the recommendation as to whether the organization should proceed with the new Product Family. If go forward is recommended, it includes documentation of the scope of the recommended product family; an approach for instantiating governance, management and methodology for this product family; and relationships, if any to existing product families and/or specific product. If go forward is not recommended, a rationale for the recommendation should be documented.
Artifacts Created | Description | How Used |
---|---|---|
Product Scope Recommendation | Documentation of the recommendation as to whether the organization should proceed with the new Product Family. If go forward is recommended, it includes documentation of the scope of the recommended product family; an approach for instantiating governance, management and methodology for this product family; and relationships, if any to existing product families and/or specific product. If go forward is not recommended, a rationale for the recommendation should be documented. | Submitted to Decisions Makers to support decision process |
Participation | Role | Assigned To |
---|---|---|
Proponent | Submitter | Individual |
Recommendation Producer | Governor | TSC Task Force |
1.1.13. Adjudicate Product Opportunity Recommendation
Artifacts Created | Description | How Used |
---|---|---|
Product Decision | Governance Artifact | Decision to act to create a new product or not |
Scope Decision | Governance Artifact | Decision on the appropriate scoping |
Participation | Role | Assigned to |
---|---|---|
Recommender | Governor | TSC |
Adjudicator | Decision Maker | Governance Board |
Author | Decision Maker | Governance Board |
1.1.14. Adjudicate Product Relationship to existing products
Artifacts Created | Description | How used |
---|---|---|
Product Family Creation Decision | Governance Artifact | Decision to act to create a new product Family or not |
Participation | Role | Assigend to |
---|---|---|
Recommender | Product Director | TSC |
Adjudicator | Decision Maker | Governance Board |
Evaluator | Decision Maker | Governance Board |