Child pages
  • Dental Interoperability Investigative Project
Skip to end of metadata
Go to start of metadata

Warning:

Do not launch ANY of the links while your are in create or edit mode. There is a good chance all of your work will be gone.


Template Usage Information:

  1. Project Name and ID


Dental Care Coordination

Enter the name of the project here: Dental Interoperability Investigative Project

Project ID: 1482

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 tscpm@HL7.org); 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.


 

NO

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

 

N/A

 

U.S.

Metric

 

Both

 

Investigative Project (aka PSS-Lite) YES

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)

Patient Care

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 periodMonthly & at WGMs

 Other Involvement. Specify details here: Web calls with WG members per interest level and content development / incorporation.

2.c. Project Team

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

Project facilitator (1Mandatory)

Todd Cooper

Other interested parties and their roles

WGs interested in monitoring and engaging as appropriate / needed):

Attachments, EHR, Health Care Devices, mHealth, Imaging Integration, Orders & Observations, Pharmacy, Structured Documents

Laura Heermann Langford (PC WG Co-Chair, primary sponsor lead)

International Coordination"

Dr. Yi Byoungk-Kee (South Korea, International Council representative)

Paul Knapp (Canada, worked closely with the Canadian Dental Association

Line Saele (Norway, coordinate FHIR-based dental interoperability work in Norway, International Council representative)

Catherine Chronaki (HL7 Europe, facilitating engagement of dental-related activities in Europe, especially at HL7 Portugal, and with other agencies)

Multi-disciplinary project team (recommended)


     Modeling facilitator

David Hay (esp. for FHIR tool usage)

     Publishing facilitator

Todd Cooper

     Vocabulary facilitator

Jean Narcisi

     Domain expert rep

Jean Narcisi, Nancy Orvis


     Business requirement analyst


     Conformance facilitator (for IG projects)


     Other facilitators (SOA, etc)




Implementers (2Mandatory 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) N/A (investigative project)

2) 

3. Project Definition

3.a. Project Scope


Dental interoperability investigative project will work with the HL7 community (experts and working groups) to identify and storyboard dental informatics related use cases that illuminate the potential value for exchanging granular dental health information to enable a new generation of digital health solutions. Initial topic areas range from care coordination, especially between dentist practices and healthcare organizations (e.g., hospital-based emergency care), EHR integration, imaging integration, documents - both general CDA and attachments, lab results, medication lists, patient administration (especially benefit discovery / approval), ... to analytics and decision support. The potential landscape is very large and opportunities abound. Thus this investigational project will collect, organize and analyze cross-paradigm use cases, and identify the highest value interoperability standards projects that should be pursued.

This effort will also be pursued jointly with the American Dental Association (ADA) to facilitate engagement of HL7-external subject matter experts. There are also ADA dental informatics standards that will help inform the "foundation" upon which joint ADA-HL7 interoperability projects might be built, including SNODENT (dental component of SNOMED).

The project will also draw on HL7's international community to ensure that the storyboards reflect the challenges around the world. This includes engagement of current dental related work through HL7 international affiliates in Canada, Korea, Norway and Portugal.


3.b. Project Need


Around the world, the state of standardized interoperable dental information exchange is the same: Little to none exists. The only business needs that have resulted in any significant standardization and implementation have to do with the fairly minimum amount of information that is needed to trigger service reimbursement payments from both private and public payors. When discussing the possibilities around interoperable dental health and care information, though, it is clear that were this capability realized, then significant improvements in health quality, care quality, safety, efficiency ... could be realized by all stakeholders - especially the patients. When this is coupled with the current industry movement toward knowledge-based technologies, including analytics (predictive & population health), artificial intelligence (integrating new measures for new indicators), personalization / precision medicine (genomic and other information), and even blockchain (e.g., for "smart contracts" between service providers, recipients and payors) - significant value can be realized from even the simplest movement toward the interoperable, seamless exchange of oral health and dental care information.

This investigational project will facilitate identification of the potential opportunities that exist in this area as well as identification of the highest value, foundational standards projects that should be pursued.


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. 

Yes

X

No

Unknown


3.d. External Drivers


This project is intended to be complete by the end of 2018, in order that the recommendations can be reviewed and actioned during the January 2019 HL7 WGM.


3.e. Project Objectives / Deliverables / Target Dates

Within each row, enter the explicit work product(s) / objective(s).  Indicate their target date at the right in WGM/Ballot Cycle format.  Include the project end date as the last objective (for standards projects, the end date will be the projected ANSI approval date). 

Target Date(in WGM or ballot cycle format, e.g.

‘2017 Sept WGM’ or

‘2017 Jan Ballot’)

Investigative Project Report (with recommendations)

2018 DEC 31

Example: Submit for STU Ballot(First Ballot Cycle)

n/a

Example: Complete STU Reconciliation

n/a

Example: Submit for 2nd STU Ballot

n/a

Example: Request STU Publication

n/a

Example: STU Period – 12 months

n/a

Example: Submit for Normative Ballot

n/a

Example: Complete Normative Reconciliation

n/a

Example: Submit Publication Request

n/a

Example: Receive ANSI Approval

n/a

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.

January 31, 2019


3.f.   Common Names / Keywords / Aliases


Dental Interop, DIIP (Dental Interoperability Investigative Project), oral health, dentist


3.g. Lineage


N/A

3.h. Project Dependencies


Enter any dependencies or the name & Project Insight ID of project(s) that this project is dependent upon to achieve its objectives: None
 

Projects and their Project Insight IDs can be found via http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?ref=common


3.i.   HL7-Managed Project Document Repository Location


Projects must adhere to the TSC's guidelines (which were approved on 2016-04-04 and summarized in Appendix A).

A template to create a Project Page on the HL7 Wiki is available at: http://wiki.hl7.org/index.php?title=Template:Project_Page.

Enter the SPECIFIC URL of the HL7-MANAGED SITE where supporting project documents, deliverables, ballot reconciliation work and other project information will be kept
Dental Interop Home


3.j.   Backwards Compatibility


Are the items being produced by this project backward compatible?

Yes

?

No

Unknown

X

N/A

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)

Yes

No

Unknown

X

N/A



If you check no, please explain the reason:

If desired, enter additional information regarding Backwards Compatibility.

N/A


3.k. External Vocabularies


Will this project include/reference external vocabularies?


Yes


No


Unknown

X

N/A

If Yes, please enter the vocabularies:


4. Products (check all that apply)



Arden Syntax


V2 Messages – Administrative


Clinical Information Modeling Initiative (CIMI)


V2 Messages - Clinical


Clinical Context Object Workgroup (CCOW)


V2 Messages - Departmental


Domain Analysis Model (DAM)


V2 Messages – Infrastructure


Electronic Health Record (EHR) Functional Profile


V3 Domain Information Model (DIM / DMIM)


FHIR Extensions


V3 Documents – Administrative (e.g. SPL)


FHIR Implementation Guide (enter FHIR product version below)


V3 Documents – Clinical (e.g. CDA)


FHIR Profiles (enter FHIR product version below)


V3 Documents - Knowledge


FHIR Resources


V3 Foundation – RIM


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


V3 Foundation – Vocab Domains & Value Sets


Logical Model


V3 Messages - Administrative


New/Modified/HL7 Policy/Procedure/Process


V3 Messages - Clinical


New Product Definition (please define below)


V3 Messages - Departmental


New Product Family (please define below)


V3 Messages - Infrastructure


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


V3 Rules - GELLO

x

White Paper


V3 Services – Java Services (ITS Work Group)


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


V3 Services – Web Services (SOA)

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


For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?



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


X

Specify external organization in Sec. 6 below;





Externally developed IG is to be (select one):


White Paper (select one):


Adopted  - OR -

?

Endorsed


Balloted Informative OR

X

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


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


Comment (aka Comment-Only)


Joint Ballot (with other SDOs)

Informative


X

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

STU to Normative     - OR -

Normative (no STU)











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



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?


Yes

X

No


6. Project Logistics

6.a. External Project Collaboration


Include SDOs or other external entities you are collaborating with, including government agencies as well as any industry outreach.  Indicate the nature and status of the Memorandum of Understanding (MOU) if applicable.

The American Dental Association (ADA) will be engaging their community of subject matter experts throughout the world to provide content for this project, as well as editorial resources to ensure that it is completed within the planned time frame.

For projects that have some of their content already developed:

How much content for this project is already developed?

0%

Was the content externally developed ? :

N

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

x

Yes

No


6.b. Realm


X

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.  Provide explanation/justification of realm selection. 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.

This investigative project is intended to be Universal and to engage both HL7 international affiliates as well as other international dental informatics subject matter experts.


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

 

Stakeholders

 

Vendors

 

Providers

X

Clinical and Public Health Laboratories

X

Pharmaceutical

X  

Clinical and Public Health Laboratories

  

Immunization Registries

X  

EHR, PHR

X  

Emergency Services

  

Quality Reporting Agencies

X  

Equipment

X

Local and State Departments of Health

X  

Regulatory Agency

  

Health Care IT

X

Medical Imaging Service

X

Standards Development Organizations (SDOs)

X

Clinical Decision Support Systems

X

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

X  

Payors

X  

Lab

  

Other (specify in text box below)

  

Other (specify in text box below)

X  

HIS

  

N/A

  

N/A

  

Other (specify below)


 

 


  

N/A

 

 


Other:  Indicate other stakeholders, vendors or providers not listed above.










6.d. Project Approval Dates

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

2018-10-04

Administrative review – in parallel with Work Group Approval

Co-Sponsor Group Approval Date


List each Co-Sponsor and their Approval Date



Family Management Group Approval Date(s)

CIMI Projects: CIMI Management Group

CIMI MG Approval Date

N/A

CDA Projects: CDA Management Group

CDA MG Approval Date

N/A

FHIR Projects: FHIR Management Group

FMG Approval Date

N/A

V2/Publishing Projects: V2 Management Group

V2 MG Approval Date

N/A

US Realm Projects: US Realm Steering Committee Approval
(Email WG approved PSS to: tscpm@HL7.org)

USRSC Approval Date

N/A

Affiliate Specific Projects: Affiliate Approval Date

Affiliate Approval Date

N/A

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

Steering Division (of Primary Sponsor WG) Approval Date:

SD Approval Date

2018-11-09

Last PBS Metrics Score:

X

 Green


 Yellow


 Red

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


 Yes


 No

ARB and Steering Division approval may be in parallel

Architectural Review Board Approval Date:

(required for externally developed content)

ARB Approval Date

N/A

TSC Approval

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

Yes

No

 N/A


Technical Steering Committee Approval Date:
(Email SD WG approved PSS to: tscpm@HL7.org)

TSC Approval Date

Nov 19, 2018