Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1.   Project Name and ID

EHR System Dental Functional Profile

Project ID: 1406

Complete this section for all “Direct to Normative” ballot projects and when a project proceeds from “Informative to Normative” or “STU to Normative”.

Forward PSS to the TSC (via; this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission.


TSC Notification:  Informative/STU to Normative 

Date:  Submission date


- or -                     Direct to Normative (no STU) (includes reaffirmations)       


Identify ISO, IEC or ISO/IEC standard to be adopted in text box below

Enter info here if an ISO, IEC, or ISO/IEC Standard is to be adopted as an American National Standard; Enter the designation of the standard(s) to be adopted:

Includes text from ISO, IEC or ISO/IEC standard: Check here if this standard includes excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption.




Select the unit of measure used in the standard; if no measurements are in the standard, select N/A









Investigative Project (aka PSS-Lite)

Date : 

Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition. Sections 1-Project Name, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3e-Project Objectives/Deliverables/Target Dates, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required for Investigative Project. 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.

2. Sponsoring Group(s) / Project Team

2.a. Primary Sponsor/Work Group

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

Electronic Health Records Work Group

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
 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 (1Mandatory)

Gregory Zeller, Patrick Cannady

Other interested parties and their roles

Multi-disciplinary project team (recommended)

     Modeling facilitator

Andrew Casertano

     Publishing facilitator

Mark Janczewski, John Ritter

     Vocabulary facilitator

Jean Narcisi

     Domain expert rep

Gregory Zeller, Jean Narcisi, Patrick Cannady

     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) Zack Church (Henry Schein)

2) Stacey Steinbeck (XLDent)

3. Project Definition

3.a. Project Scope


Currently, HL7's EHR System Functional Model R2 contains no dentistry-specific functional requirements and no US Realm Dental Functional Profile has ever been initiated, let alone completed a ballot process. As a result, there is no standard, computable EHR Dental Functional Profile that can be used to create RFPs, define certification criteria, or design EHR systems for the dental setting. This project will complete a much-needed oral health portion of HL7's EHR System Functional Model.

The ADA Standards Committee on Dental Informatics (SCDI), an Associate SDO per the current ADA-HL7 SOU, developed a Dental EHR System Functional Model, ADA Standard No. 1067, under the terms of a predecessor agreement or agreements in effect 2010-2012. ADA Standard 1067 incorporated relevant conformance requirements in HL7 EHR-S FM R1.1 with the addition of unique conformance requirements identified by SCDI volunteers.

In addition to a new HL7 Dental Functional Profile of the EHR System Functional Model, the ADA SCDI would like to revise Standard 1067 and bring it into harmony with EHR-S FM R2.

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

None at this time.


3.i.   HL7-Managed Project Document Repository Location

3.j.   Backwards Compatibility


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;

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)

This will be a profile of the EHR-S Functional Model + Revision to an Associate SDO 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.)

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


6.a. External Project Collaboration

ADA Standards Committee on Dental Informatics (SCDI)

For projects that have some of their content already developed:

How much content for this project is already developed?

Difficult to say, 25-40%? Some R1.1 content already identified (in ADA SCDI Standard No.1067) for this profile that can be quickly added to an R2 profile using the HL7 EHR-S FM Profiling tool. An unknown number of unique dental requirements with no reference to either R1.1 or R2 are in ANSI/ADA Standards 1067 and 1084 and will need to be included in this dental functional profile.

Was the content externally developed ? :

Yes and No, see above.

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




6.b. Realm


- OR -


Realm Specific:  U.S. Realm


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

US Realm


Click here to go to HL7 Project Scope Statement Instructions#Appendix A for more information regarding this section.
Approvals are by simple majority vote of the approving body

Sponsoring Work Group Approval Date:

WG Approval Date


Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date



US Realm Projects: US Realm Steering Committee Approval
(Email WG approved PSS to:

USRSC Approval Date


Affiliate Approval Date (for Affiliate Specific Projects):

ADA SCDI Approved


Submit PSS to Steering Division after all of the above approvals are received

Steering Division (of Primary Sponsor WG) Approval Date:

SD Approval Date


Last PBS Metrics Score:




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



ARB and Steering Division approval may be in parallel

Architectural Review Board Approval Date:

(required for externally developed content)

ARB Approval Date

TSC Approval

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




Technical Steering Committee Approval Date:
(Email SD WG approved PSS to:

TSC Approval Date