Project Summary for EHR-S FM/FP Profile Designer Tool (for PHR-S FM)
Visit Project Insight to see the full project details. *
Project Details
Number | 1134 View Ballot Items List (with NIBs) |
---|---|
Name | EHR-S FM/FP Profile Designer Tool (for PHR-S FM) |
Sponsor(s) | Electronic Health Records Work Group |
Co-Sponsor(s) | PEST Work Group |
Steering Division | Administrative |
Description | The finalization of the EHR-S FM Profile Design Tool consists of three distinguishable parts: 1. PHR-S FM: After the completion of the EHR-S FM Profile tooling in 2013 and 2014, the EHR WG wants to include the PHR-S FM and FPs in the tool. The first step is the import of the PHR-S FM into EA (in the same way as it was done for the EHR-S FM R2). An extension for the PHR-S FM will be created that conforms to the extension that exists for the EHR-S FM R2. In addition, MAX publication formats and XML converters will be created comparable to the EHR-S FM publication format. The second step is the further development of the extension to accommodate the development, management and balloting of PHR-S Functional Profiles, which are derived from the PHR-S FM. 2. Translation: This part of the project will identify, define and implement the requirements necessary for the EHR-S FM Profiling Tool to support the translation of the elements in the Functional Model and the development of a Realm Functional Profile in the country's native language. Baseline of the project is that there will be no changes in the tool design. The translation of the functional models and/or the functional profiles themselves is out of scope. 3. Framework: The identification, definition and implementation of the requirements necessary for the support of a framework from which a functional model can be developed. The framework can be envisioned via a three tiered approach: the framework contains sections which can be included in functional models. From these models profiles can be derived. The framework is a superset of sections, functions and conformance criteria. This creates the potential to use the tool for other domains such as laboratory or pharmacy. |
Project Facilitator | William Goossen |
Status | Archived |
SD Approval Date | Sep 15, 2014 |
TSC Approval Date | Oct 6, 2014 |
Type | Vendor Contract |
Objectives / Deliverables | Create user stories for defining the requirements - Target: First October 2014, and a bi-monthly follow up Identification of requirements based on the user stories - Target: First November 2014, and then each a month after the user stories Implementation of the requirements - Target: First January 2015 WGM, and then following additional user stories Development of user guides for users - Target: First January 2015 WGM, and then following additional implementations Adjustment of the tutorial presentation - Target: January 2016 Progress reports in the conference calls of the EHR WG and the wiki. - Target: Whenever a user story / requirements / implementation is ready Work in progress will be uploaded on Box and deliverables will be available on GForge. - Target: Continues during whole project Initial support to key users in installing and initial use of the tool. - Target: Jan WGM 2015, May WGM 2015, Sept WGM 2015, Jan WGM 2016, May WGM 2016 Acceptance test set up and carry out - Target: May WGM 2016 Project End Date (all objectives have been met) - Target: September 2016 Not in scope: Giving tutorials or webinars. |
Next Milestone Date | 2018 May WGM |
Project End Date | 2018 May WGM |
Project Intent | N/A (Project not directly related to an HL7 Standard) |
Project Need | It is difficult to manage existing functional models and functional profiles. Additionally, the development of new functional models and functional profiles becomes very complex because the number of functions has increased (from previous releases) and the need for new functional models is growing (e.g. Laboratory-S FM). The need for a manageable PHR-S FM and functional profiles derived from the PHR-S FM is growing. The development of PHR's is growing and more and more (patient) organisations desire a standards-based method of defining PHR System requirements. Until now, the PHR-S FM and FP have been left out for reasons of having a slightly different organisation and content. The third need is the need on tool support for translation of the functional models and the development of Realm functional profiles in the various HL7 affiliate countries. Many of them want the profiles and models available in their own language and projects are being prepared in several countries. Since the need for new functional models is growing the framework approach like a superset of sections, functions and conformance criteria from which users can choose to develop a new functional model becomes obvious because of motives as increasing efficiency, time-savings and higher effectiveness. Users can use the framework to develop their functional model based on the experience of year's work that is already been done with the EHR-s FM and the PHR-S FM, and the first experiences with the current tool. Subsequently new functional profiles can be derived from that new functional model. By including the traceability between the framework, the functional models and the functional profiles, a manageable whole of models and profiles will arise. |
Implementers | 1) HL7 International, internal tooling for EHR WG 2) HL7 Italy (contact Giorgio Cangioli) 3) HL7 Netherlands |
Security Risks | |
External Drivers | |
Common Names / Keywords/ Aliases | |
Lineage | |
Dependancies | This project depends on the collaboration with the EHR WG and Tooling WG, and for the translation part on HL7 Europe and the HL7 affiliates Italy and/or the Netherlands. |
Project Document Repository |
http://wiki.hl7.org/index.php?title=EHRs_FM_Profiling_Tool HL7 gforge. http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/ |
Backwards Compatibility | N/A |
External Vocabularies | |
Products | |
Joint Copyright? | No |
External Pjt Collaborators | |
Realm | Universal |
HL7 Affiliate | |
Stakeholders | N/A |
Vendors | EHR, PHR; Health Care IT |
Providers | Healthcare Institutions (hospitals, long term care, home care, mental health) |
Ballot Cycle Info | |
Misc Notes | 2020 Sept: G. Dickinson: Complete. PMO archiving project. 2018 Jan: M. Brody provided the PMO with a 3-Year Plan document which indicated that the EHR WG was still working on this project. The EHR WG Decided early 2014 that any conversion from R1.1 profiles to R2 profiles is not required. That part of the work was changed in working with RMES, MU, PHR and Translation teams to assist. |
U.S. Govt Interest? | |
USRSC Approval | |
FMG Approval | |
ARB Approval | |
Start Date | Jul 15, 2014 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.