1. Project Name  and ID

Project Name:Reaffirm HL7 Version 3 Standard: Master File/Registry Infrastructure R1

Project ID:


Date : 


Date : 

2. Sponsoring Group(s) / Project Team

2.a.Primary Sponsor/Work Group:
(1 (And Only 1) Allowed)

 Infrastructure and Messaging (InM)

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

(Enter co-sponsor approval dates in Section 6.c 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: 

<other involvement>

2.c Project Team

Project facilitator (1Mandatory)

Anthony Julian

Other interested parties and their roles

<Interested Party & Role>

Multi-disciplinary project team (recommended)


       Modeling facilitator


       Publishing facilitator


       Vocabulary facilitator


       Domain expert rep


       Business requirement analyst


       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

2.a.    Project Scope

Reaffirm HL7 Version 3 Standard: Master File/Registry Infrastructure R1

2.b.   Project Need


The Master File / Registry domain comprises the classes and attributes needed to support Master Files and Registries. It does so by providing a Trigger Event Control Act that can be associated through a subject participation either with an entity (a Role) or with an act.

 This domain focuses on the Master File / Registry specific extensions to the generic Trigger Event Control Act. Refer to the Message Control Act Infrastructure Introduction for general details on Trigger Event Control Acts.

2.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.









2.d.   External Drivers

Describe any external schedules or calendars which may not be known outside of the project team that are driving target dates for this project.

2.e.    Project Objectives / Deliverables / Target Dates


Target Date

Submit for Normative Ballot

2018 May Ballot

 Complete Normative Reconciliation

2018 May WGM

Submit Publication Request

2018 June

Receive ANSI Approval

2018 June

Project End Date (all objectives have been met)

Note:  For PSS-Lite/Investigative Project, End date must be no more than two WGM cycles, e.g. project initiated at January WGM must complete investigation by September WGM.

2018 June

2.f.       Common Names / Keywords / Aliases


2.g.   Lineage

If your project creates a Post-Release 1 version; indicate the name of the prior product and if it is supplanting, replacing or coexisting with a previous release.

2.h.   Project Dependencies

2.i.       Project Document Repository Location


2.j.       Backwards Compatibility

Are the items being produced by this project backward compatible?






















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:

If desired, enter additional information regarding Backwards Compatibility.

2.k.    External Vocabularies

Will this project include/reference external vocabularies?

























If yes, please list the vocabularies:


  1. Products (check all that apply)


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



V3 Domain Information Model (DIM / DMIM)


Arden Syntax



V3 Documents – Administrative (e.g. SPL)


Clinical Context Object Workgroup (CCOW)



V3 Documents – Clinical (e.g. CDA)


Domain Analysis Model (DAM)



V3 Documents - Knowledge


Electronic Health Record (EHR) Functional Profile



V3 Foundation – RIM


Logical Model



V3 Foundation – Vocab Domains & Value Sets


V2 Messages – Administrative



V3 Messages - Administrative


V2 Messages - Clinical



V3 Messages - Clinical


V2 Messages - Departmental



V3 Messages - Departmental


V2 Messages – Infrastructure



V3 Messages - Infrastructure


FHIR Implementation Guide



V3 Rules - GELLO


FHIR Profiles



V3 Services – Java Services (ITS Work Group)


FHIR Resources



V3 Services – Web Services (SOA)


New/Modified/HL7 Policy/Procedure/Process



White Paper


New Product Definition





New Product Family




If you checked New Product Definition or New Product Family, please define below:


  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)


If revising a current standard, indicate the following:

-   Name of the standard being revised

-   Date it was published (or request for publication, or ANSI designation date)

-   Rationale for revision

-   The relationship between the new standard and the current standard (is it designed to replace the current standard, a supplement to the current standard, etc.)

4.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)


 Reaffirmation of Normative ANSI Standard

If necessary, add any additional ballot information here.  If artifacts will be jointly balloted with other SDOs, list the other groups.

4.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

5.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)














5.b.   Realm


Universal     - OR -



Realm Specific




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


Enter “U.S.” or name of HL7 affiliate(s) here.  For projects producing deliverables applicable to multiple realms, document those details here.

For Investigative projects, indicate if the project is planned to be Realm Specific or Universal, if known. Work Groups are encouraged designating project a Universal project initially, and discover which Realms can contribute to the work effort during the discovery phase of the project.  Note: This status is subject to change during the investigative process. 

5.c.    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:

WG Approval Date 2017-01-03

Co-Sponsor Group Approval Date

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


FHIR Project: FHIR Management Group Approval Date:


Architectural Review Board Approval Date:


Steering Division Approval Date :

SD Approval Date CCYY-MM-DD

Last Work Group Health:







PBS Metrics and Work Group Health Reviewed? (required for SD Approval if not green)





Technical Steering Committee Approval Date:

TSC Approval Date CCYY-MM-DD

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