Page tree
  1. Project Name and ID



African Participation Outreach

Project ID:



TSC Notification Informative/STU to Normative          

Date : 

Check this box when the project proceeds from Informative to Normative or STU to Normative status.  Forward to the TSC for notification, as this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.  



Investigative Project

Date:  12/13/2017

Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition.  Sections in bold outline are mandatory for project approval of an investigative project; all other sections are optional. Sections 1-Project Name and Scope, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3g-Project Objective, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required.

Investigative Project specific instructions are highlighted in yellow.

An investigative project must advance in two WGM cycles, requiring a full scope statement.  Otherwise the project will be closed.

  1. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

Primary Sponsor/Work Group
(1 (And Only 1) Allowed)

International Council

2.b. Co-sponsor Work Group(s)

Co-sponsor Work Group(s)

(Enter co-sponsor approval dates in Section 6.d Project Approval Dates)



Indicate the level of involvement that the co-sponsor will have for this project:


Request formal content review prior to ballot


Request periodic project updates. Specify period: 

Monthly, at WGMs, etc.


Other Involvement. Specify details here: 


2.c. Project Team

All names should have confirmed their role in the project prior to submission to the TSC.

Project facilitator ( 1 Mandatory )

AbdulMalik Shakir

Other interested parties and their roles

Virginia Lorenzi, Diego Kaminker, John Ritter

Multi-disciplinary project team (recommended)


Modeling facilitator


Publishing facilitator


Vocabulary facilitator


Domain expert rep

Wilson Ramos, John Gachago, Gora Datta

Business requirement analyst

Salimah Shakir

Conformance facilitator (for IG projects)


Other facilitators (SOA, etc.)




Implementers (2 Mandatory for STU projects)

FHIR Project Note: The implementer requirement will be handled by the “balloting” project.  Therefore work groups do not fill out the above section.  However, feel free to list implementers specific to your work group’s resources if you know of any.



  1. Project Definition

3.a. Project Scope

Establish formal channels of communication and outreach to regions of the African continent with the end goal of raising awareness of HL7, increasing the use of HL7 on the continent, and eventually establishing HL7 affiliate organizations in Africa.

3.b. Project Need

HL7's international affiliates are mainly from developed nations in Europe, Asia, and the United States with none from Africa. The purpose of this project is to establish formal channels of communication and outreach to regions of the African continent with the end goal of raising awareness of HL7, increasing the use of HL7 on the continent, and eventually establishing HL7 affiliate organizations in Africa. The African continent is engaged in significant national and regional eHealth projects and initiatives. Leveraging the collective experience, healthcare informatics skills, and technical resources of HL7 International would help to accelerate efforts underway and reduce the risk associated with establishment of system interoperability capabilities among the diverse set of implementations.

3.c. Security Risks

Will this project produce executable(s), for example, schemas, transforms, style sheets, executable program, etc.  If so the project must review and document security risks. Refer to the Cookbook for Security Considerations for additional guidance, including sample spreadsheets that may be used to conduct the security risk assessment .











3.d. External Drivers


3.e. Project Objectives / Deliverables / Target Dates


Target Date

Establish a project charter and detailed project plan

Jan 2019 WGM

San Antonio, TX

Develop a communication plan (talking points, materials, resource allocation)

Feb 2019

Identify regional and national points of contact, including government entities, standing informatics and scientific communities, and eHealth initiatives project teams.

Mar 2019

Survey and outreach to potential funding sources. Determine qualifications, process, and time constraints for requesting funds.

Apr 2019

Identify national and regional eHealth initiatives underway in the continent.

May 2019 WGM

Montreal, Canada

Provide a webinar targeted to the points of contact to familiarize them with the project and to gauge the level of interest.

Jul 2019

Develop plans for in-person HL7 fact finding engagements with selective leaders or liaisons of regional eHealth initiatives.

Sep 2019

Atlanta, GA

Prepare a budget and funding plan to support the in-person engagement.

Jan 2020 WGM

Sydney, Australia

Obtain HL7 BOD approval of project budget and funding plan

Feb 2020

Finalize plans and execute the in-person HL7 fact finding team engagement with selective leaders or liaisons of regional eHealth initiatives

Apr 2020

Prepare a post engagement brief for the HL7 BOD with findings and recommendations for further action.

May 2020 WGM

San Antonio, TX

3.f.    Common Names / Keywords / Aliases


3.g. Lineage


3.h. Project Dependencies


3.i.    Project Document Repository Location


3.j.    Backwards Compatibility

Are the items being produced by this project backward compatible?





















If you check 'Yes' please indicate the earliest prior release and/or version to which the compatibility applies:


For V3, are you using the current data types? 

(Refer to TSC position statement on new projects using R2B for more information on the current V3 data types)





















If you check 'No' please explain the reason:


3.k. External Vocabularies

Will this project include/reference external vocabularies?

























If yes, please list the vocabularies:


  1. Products (check all that apply)


Arden Syntax



V2 Messages – Administrative


Clinical Context Object Workgroup (CCOW)



V2 Messages - Clinical


Domain Analysis Model (DAM)



V2 Messages - Departmental


Electronic Health Record (EHR) Functional Profile



V2 Messages – Infrastructure


FHIR Extensions



V3 Domain Information Model (DIM / DMIM)


FHIR Implementation Guide



V3 Documents – Administrative (e.g. SPL)


FHIR Profiles



V3 Documents – Clinical (e.g. CDA)


FHIR Resources



V3 Documents - Knowledge


Guidance (e.g. Companion Guide, Cookbook, etc.)



V3 Foundation – RIM


Logical Model



V3 Foundation – Vocab Domains & Value Sets


New/Modified/HL7 Policy/Procedure/Process



V3 Messages - Administrative


New Product Definition (please define below)



V3 Messages - Clinical


New Product Family (please define below)



V3 Messages - Departmental


Non Product Project - (Educ. Marketing, Elec. Services, etc.)



V3 Messages - Infrastructure


White Paper



V3 Rules - GELLO





V3 Services – Java Services (ITS Work Group)


Creating/Using a tool not listed in the HL7 Tool Inventory



V3 Services – Web Services (SOA)

  1. Project Intent (check all that apply)


Create new standard



Supplement to a current standard


Revise current standard (see text box below)



Implementation Guide (IG) will be created/modified


Reaffirmation of a standard



Project is adopting/endorsing an externally developed IG:


New/Modified HL7 Policy/Procedure/Process



Specify external organization in Sec. 6 below;


Withdraw an Informative Document



Externally developed IG is to be (select one):


White Paper (select one):



Adopted  - OR -





Balloted Informative OR


Non-balloted WG White Paper



N/A  (Project not directly related to an HL7 Standard)

5.a. Ballot Type (check all that apply)


Comment (aka Comment-Only)



Joint Ballot (with other SDOs)





N/A (project won’t go through ballot)


STU to Normative     - OR -


Normative (no STU)




5.b. Joint Copyright

Check this box if you will be pursuing a joint copyright.  Note that when this box is checked, a Joint Copyright Letter of Agreement must be submitted to the TSC in order for the PSS to receive TSC approval.

Joint Copyrighted Material will be produced?









  1. Project Logistics

6.a. External Project Collaboration

For projects that have some of their content already developed:

How much content for this project is already developed?

Indicate % here

Was the content externally developed (Y/N)? 

If Yes, list developers

Is this a hosted (externally funded) project? 
(not asking for amount just if funded)













6.b. Realm


Universal     - OR -



Realm Specific




Check here if this standard balloted or was previously approved as realm specific standard



6.c. Stakeholders / Vendors / Providers

This section must be completed for projects containing items expected to be ANSI approved, as it is an ANSI requirement for all ballots








Clinical and Public Health Laboratories




Clinical and Public Health Laboratories


Immunization Registries




Emergency Services


Quality Reporting Agencies




Local and State Departments of Health


Regulatory Agency


Health Care IT


Medical Imaging Service


Standards Development Organizations (SDOs)


Clinical Decision Support Systems


Healthcare Institutions (hospitals, long term care, home care, mental health)






Other (specify in text box below)


Other (specify in text box below)




National Ministries of Health


African eHealth Initiative Government and Non-Government Funding agencies


Other (specify below)




6.d. Project Approval Dates

Affiliate Approval Date (for Affiliate Specific Projects):


US Realm Steering Committee Approval Date
(for US Realm Specific Projects):


Sponsoring Work Group Approval Date:

February 1, 2018

Co-Sponsor Group Approval Date

(Copy this entire row for each co-sponsor; indicate the specific cosponsor that issued approval)

February 1, 2018

FHIR Project: FHIR Management Group Approval Date:


Architectural Review Board Approval Date:

(required for externally developed content)


Steering Division (of Primary Sponsor WG) Approval Date:


Last PBS Metrics Score :







PBS Metrics Reviewed ? (required for SD Approval if not green)





Technical Steering Committee Approval Date:


TSC has received a Copyright/Distribution Agreement (containing the verbiage outlined within the SOU), signed by both parties.