Skip to end of metadata
Go to start of metadata

NOTE: To use Track Changes, turn off "protection" by clicking on (pre-MS Word 2007) Tools > Unprotect Document or (MS Word 2007 and higher) Review > Protect Document.
PSS-Lite/Investigative Projects: Sections surrounded by a BOLD OUTLINE must be completed for approval of "Investigative Projects" (a.k.a PSS-Lite).

Project Name and ID







Podiatry Profile of EHR-S Functional Model V 2.01




Project ID: 1352




TSC Notification Informative/STU to Normative

Date :










Investigative Project

Date :









Sponsoring Group(s) / Project Team
Primary Sponsor/Work Group

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

EHR Workgroup

Co-sponsor Work Group(s)

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


Approved 2017-05-10

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:

CIMI - CIMI plans to have a representative at the weekly telephone calls



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

Attachments Work Group

Approved 2017-05-25

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:

Attachments- Dr Brody will attend the first half hour of the Attachments calls on Tuesdays at 2:30 Eastern, and Attachments will have a representative on the project calls on an as needed basis.



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

Orders and Observations
Approved 2017-05-10

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:

Orders and Observations - Dr Brody and other members of the project will attend O and O calls on a regular basis



Project Team

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

Project facilitator (1 Mandatory)

Michael L. Brody, DPM

Other interested parties and their roles

Pharmacy Work Group

Multi-disciplinary project team (recommended)


Modeling facilitator

John Ritter

Publishing facilitator

John Ritter

Vocabulary facilitator

Ted Klein

Domain expert rep

American Podiatric Medical Association (APMA)

  • Seth Rubinstein DPM (Podiatrist in Private Practice)
  • Diane Tower DPM – Staff Member

    American College of Foot and Ankle Medicine (ACFAOM)
  • Michael Warshaw DPM (Podiatrist in Private Practice)

    Podiatry Insurance Company of America – Malpractice Carrier
  • Barbara Bellione RN Director of Risk Management

    Biomedix – Manufacturer of Vascular Analysis Device
  • John Romans CEO

    Nemo Capital Partners – EHR Vendor
  • Alan Bass DPM (Podiatrist in Private Practice)

    ICS Software – EHR Vendor
  • Ken Katz CEO

    MedXpress – Qualified Clinical Data Registry
  • Michael L Brody, DPM Chief Medical Officer

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) ICS Software


2) Nemo Partners


Project Definition
Project Scope

The goal of this project is to develop a Podiatry Specific profile of the EHR-S functional model that addresses the specific needs of a Podiatrist. The scope of Podiatry in the United States is substantially broader than the scope of Podiatry in other countries; therefore, this is a US Realm project.

Project Need

Podiatry is the sub specialty that focuses on the treatment of the foot and lower extremity. There are specific examinations and documentation elements that are not currently supported by the current EHR-S Functional Model, in addition there are elements of the EHR-S Functional Model that do not apply to the practice of Podiatry. This project is needed to develop conformance criteria for a EHR System that is fit for use by a Podiatrist.

Among the issues identified are:

Improved documentation of wounds of the lower extremity for improved continuity of care and interoperability

Including the ability for an EHR system to send messages to discontinue medications, messages to indicate that OTC medications have been supplied to pharmacies and pharmacy benefit plans.

Improved ability to support Electronic Submission of Medical Documentation, Electronic Determination of Coverage, and clinical documentation with stakeholders to support both quality reporting and revenue cycle management.

Ability to support the capture of all relevant data related to joint replacements ORIF (screws and plates) and other implantable devices that have unique device identifiers and those that do not have UDI's.

Ability to support communication of accurate data and authentic records with all appropriate stakeholders

Ability to support communication of quality measure data with all appropriate stakeholders.

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.
















External Drivers

None known at this time

Project Objectives / Deliverables / Target Dates


Target Date

Complete Gap Analysis for Functional Profile

2018 Jan

Submit for Comment Only Ballot (First Ballot Cycle)

2018 May Ballot

Complete Comment Ballot Reconciliation

2018 Sept WGM

Submit for Normative Ballot

2019 Jan Ballot

Complete Normative Reconciliation

2019 May

Submit Publication Request

2019 Sept

Project End Date (all objectives have been met)

2019 Sept

Common Names / Keywords / Aliases

Podiatry Functional Profile of EHR-S Functional Model



Project Dependencies

None Known

Project Document Repository Location
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:


























External Vocabularies

Will this project include/reference external vocabularies?


























If yes, please list the vocabularies:
SNOMED, LOINC and other ontologies that deal with clinical data. We will also submit codes to SNOMED and LOINC for consideration to fill any identified gaps in coding for Podiatry.













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)


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)




This will be a profile of the EHR-s Functional Model

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)





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?









Project Logistics
External Project Collaboration









For projects that have some of their content already developed:








How much content for this project is already developed?








Was the content externally developed (Y/N)?








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

















Universal - OR -





Realm Specific









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









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)





Other (specify below)







Podiatrists – American Podiatric Medical Association



Project Approval Dates

Affiliate Approval Date (for Affiliate Specific Projects):










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

US Realm Steering Committee Date 2017-07-25









Sponsoring Work Group Approval Date:

WG Approval Date 2017-07-11









Co-Sponsor Group Approval Date
(Copy this entire row for each co-sponsor; indicate the specific cosponsor that issued approval)

CIMI Approval Date 2017-05-10
Orders and Observations Approval Date 2017-05-10
Attachments Approval Date 2017-05-25









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:

2017-10-16TSC Approval Date CCYY-MM-DD









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




















  • No labels