This wiki has undergone a migration to Confluence found Here

Difference between revisions of "EHRs FM Profiling Tool"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
  
 
===Project a summary===
 
===Project a summary===
This project, sponsored by the HL7 Tooling Workgroup and co-sponsored by the EHR Workgroup, produced a desktop tool to create EHR-S FM Functional Profiles (starting with the EHR-S FM R2), with enforced profiling rules, and exports as documents, support for and XML interchange format for reuse across profile tool instances or for use in other tools.  
+
This project, sponsored by the HL7 Tooling Workgroup and co-sponsored by the EHR Workgroup, produced a desktop tool to create EHR-S FM Functional Profiles (starting with the EHR-S FM R2), with enforced profiling rules, and exports as documents, support for and XML interchange format for reuse across profile tool instances or for use in other tools. The tool is part of the HL7 suite of tools.
<br/>The tool is part of the HL7 suite of tools.
 
 
<br/>Although the project was targeted for the EHR-S FM R2, the goal is to target the PHR-S FM also beginning with the PHR-S FM R2.
 
<br/>Although the project was targeted for the EHR-S FM R2, the goal is to target the PHR-S FM also beginning with the PHR-S FM R2.
 
<br/>The method of creating EHR-S FM Functional Profiles, using unstructured tools (spreadsheet, text processor), did not enforce moderately complex rules for creating EHR-S FM Functional Profiles leading to a very laborious manual effort that is prone to errors.  Furthermore, the methods used in the past did not easily provide methods for building on top of, merging, or updating existing profiles.  These challenges were proved to be significant barriers in the use and adoption of the EHR-S Functional Model.
 
<br/>The method of creating EHR-S FM Functional Profiles, using unstructured tools (spreadsheet, text processor), did not enforce moderately complex rules for creating EHR-S FM Functional Profiles leading to a very laborious manual effort that is prone to errors.  Furthermore, the methods used in the past did not easily provide methods for building on top of, merging, or updating existing profiles.  These challenges were proved to be significant barriers in the use and adoption of the EHR-S Functional Model.
<br />As said in the Introduction, the EHR-S FM Profile Designer Tool is built as an extension on Enterprise Architect and works with the Corporate Edition. In the same time, a project for MAX was running. Although MAX itself was out of scope the project team decided to use MAX as export format for this work, hence facilitating publishing workgroup as well. The MAX extension that was built is needed for certain functionality when creating a Functional Profile with the tool. Summarized, someone needs Enterprise Architect, corporate edition, The extension EHR-S FM Profile Designer Tool and the MAX extension.  
+
<br />As said in the Introduction, the EHR-S FM Profile Designer Tool is built as an extension on Enterprise Architect and works with the Corporate Edition. In the same time, a project for MAX was running. Although MAX itself was out of scope the project team decided to use MAX as export format for this work, hence facilitating publishing work group as well. The MAX extension that was built is needed for certain functionality when creating a Functional Profile with the tool. Summarized, someone needs Enterprise Architect, corporate edition, The extension EHR-S FM Profile Designer Tool and the MAX extension.  
 
At this moment (2017-07-03) both extensions and all the computable artifacts are available for HL7 members only and can be obtained by contacting the EHR WG co-chairs (http://www.hl7.org/Special/committees/ehr/leadership.cfm).
 
At this moment (2017-07-03) both extensions and all the computable artifacts are available for HL7 members only and can be obtained by contacting the EHR WG co-chairs (http://www.hl7.org/Special/committees/ehr/leadership.cfm).
 
<br />More general information on how to create Functional Profiles and the manuals for the tool can be found on this wiki.
 
<br />More general information on how to create Functional Profiles and the manuals for the tool can be found on this wiki.

Revision as of 09:32, 7 March 2017

EHR-S FM Profile Designer Tool

To return to the >> EHR Work Group Page
To return to the >> Tooling Work Group Page

Introduction

The HL7 EHR Work Group developed the EHR-S FM from which Functional Profiles can be derived. For both the management of the Functional Model and the Functional Profiles and the development of Functional Profiles, a tool is developed: the EHR-S FM Profile Designer Tool. The tool is built as an extension to Enterprise Architect from Sparx. The tool works with the Corporate Edition of Enterprise Architect. when someone wants to develop a Functional Profile from the EHR-S FM with the use of the tool, he needs Enterprise Architect, the extension EHR-S FM Designer Tool, and the computable artifacts to do so. Sparx has several tutorials of how Enterprise Architect works. For the EHR-S FM Designer Tool several manuals were developed. These manuals and the -How-To-Guide-, this guide describes how to create a Functional Profile, can be found on this wiki.

The wiki still contains a lot of project information from the past. This content will be removed in the coming months as the wiki will get a different purpose.

Project a summary

This project, sponsored by the HL7 Tooling Workgroup and co-sponsored by the EHR Workgroup, produced a desktop tool to create EHR-S FM Functional Profiles (starting with the EHR-S FM R2), with enforced profiling rules, and exports as documents, support for and XML interchange format for reuse across profile tool instances or for use in other tools. The tool is part of the HL7 suite of tools.
Although the project was targeted for the EHR-S FM R2, the goal is to target the PHR-S FM also beginning with the PHR-S FM R2.
The method of creating EHR-S FM Functional Profiles, using unstructured tools (spreadsheet, text processor), did not enforce moderately complex rules for creating EHR-S FM Functional Profiles leading to a very laborious manual effort that is prone to errors. Furthermore, the methods used in the past did not easily provide methods for building on top of, merging, or updating existing profiles. These challenges were proved to be significant barriers in the use and adoption of the EHR-S Functional Model.
As said in the Introduction, the EHR-S FM Profile Designer Tool is built as an extension on Enterprise Architect and works with the Corporate Edition. In the same time, a project for MAX was running. Although MAX itself was out of scope the project team decided to use MAX as export format for this work, hence facilitating publishing work group as well. The MAX extension that was built is needed for certain functionality when creating a Functional Profile with the tool. Summarized, someone needs Enterprise Architect, corporate edition, The extension EHR-S FM Profile Designer Tool and the MAX extension. At this moment (2017-07-03) both extensions and all the computable artifacts are available for HL7 members only and can be obtained by contacting the EHR WG co-chairs (http://www.hl7.org/Special/committees/ehr/leadership.cfm).
More general information on how to create Functional Profiles and the manuals for the tool can be found on this wiki.

Project Team

William Goossen, internal projectleader
Michael van der Zel, modeller
Andy Stechishin, tester
Anneke Goossen, documenter

Meeting Information

Conference Calls
The project team has a weekly conference call on Monday evening.

Members of the project team will join the regular conference calls of the WG EHR and the WG Tooling.

Project Documents

HL7 Project Scope Statement - EHR-S FM Profiling Tool.doc

  • The project scope statement was approved by the EHR and Tooling Workgroups in November 2011.

Work Group Testing Objectives

The Work Group needs to exercise the EHR-S FM Tool in Enterprise Architect to ensure that the tool deliverables meet the requirements specified for this phase of the project. The first prerequisite to performing any testing is having a working installation of Enterprise Architect. Beyond that the testers need to focus on usability (both by technical and non-technical users), impressions on overall capabilities (does the tool manage the expected and agreed upon aspects of the process), stability (is the tool stable and not crash) and correctness (where detailed specification exist, like validations, is the tool operating according to those specifications).

The following steps should be performed to verify the tool according to the above parameters:

  1. Install the tool into Enterprise Architect (both the FM model extension and the MAX import/export extension)
  2. Load the EHR-S FM eap file
  3. Browse the EHR FM using the tool
  4. Update components, sections, headers, functions and/or conformance criteria, of the EHR-S FM using the tool
  5. Export the EHR-S FM to MAX (From the MAX export a html and pdf can be created.the work on this is not finished yet, but will be ready by the Atlanta WGM)
  6. Validate the EHR-S FM

The project team is providing a spreadsheet for the tester to record any issues/impressions. The spreadsheet will be combined and the issues will be triaged with the EHR WG and the project team. The issue list will then be formally maintained using the Tracker in the GForge project area.

Note: this is the testing of the EHR-S FM tool as it will be delivered for phase 1. The scope of phase 1 is described in chapter 1 Overview.

Project Status

Project Plan Draft

This project is slated to follow an iterative development pattern. Below is an initial draft for the first iteration.

  1. Functional requirement definition
    • EHR-S FM Chapter 2 (Conformance rules - Tool business rules)
    • Define user experience requirements
    • Functional Brainstorm and Survey (define initial release functional requirements
  2. Existing tool analysis
  3. Functional Specification
  4. Technical Specification
  5. Development
  6. Testing
  7. Release


Dependencies


The project depends on the availability of the following materials:

  • Full XML export from the EHR-S FM spreadsheet
  • This material has been made available Dec 31, 2012.
  • Validation rules for the EHR-S FM
  • The validation rules where provided in September 2012 and used as input to the validation function.

Current Activities in Tool Creation Phase 1

Different steps in tool creation phase 1

The figure shows the numbers that will generate the various materials to create the tool.
1. Exporting XML from the EHR-S FM spreadsheet.
2. EHR-S FM design pattern development.
2. EHR-S FM XML to UML mapping.
3. Inclusion of the EHR-S FM in Enterprise Architect.
4. Completing the set of validation rules for EHR-S FM.
5. Generate validation report to tool user.
6. Documentation to export EHR-S FM from Enterprise Architect (publication templates).
7. Exporting EHR-S FM documentation from Enterprise Architect (ballot artefacts). In addition there will be a user guide containing:
User documentation for EHR-S FM import/installation in Enterprise Architect.
Documentation to use EHR-S FM in Enterprise Architect.

What has been done till end of September 2012


The project team has held weekly Skype conference calls to discuss the goals, plan, deliverables, work and progress.
A Github repository for the source code was established for the project team, which at the end of the project will be handed over to HL7
A MS Groove folder was established for all other files, meeting agenda’s and reports, links etc, for internal use.
The HL7 Sept 2012 WGM was prepared for, through a PowerPoint presentation, delivered to Tooling WG, EHR WG and tooling planning meeting.
Dependency was discussed, and consequences expressed. In case that would become a blockade, report to HL7 before December 1.
The EHR workgroup members have been asked for validation rules. These where provided, and discussed in the conference call Sept 25. A draft document with validation rules was created.
Initial efforts to create the wiki page for the project have been undertaken and we will follow up with the EHR WG how to arrange that.
XML to UML import meta model was available for R1.1. This existing material is changed to EHR-S FM R2. Our current version of the UML meta model of R2 is v 3.2. This will definitely change when the import, meta model and UML representation and mapping are 100%.

Deliverables of End of September 2012


Report 1.
The May 2012 XML file, as then was generated by Mr. Corey Spears has been included in this package. That is not so much a delivery, but an important baseline file for the current project. All additional material provided here is derived from that file. (# 1 in figure 1). < File EHRS_FM_R2_N1_C3_FunctionList_2012MAY.XML />
The current Sept version of the UML representation of the EHR-S FM as derived from the May 2012 XML version. This is available as an 90 to 95% ready Enterprise Architect Project EAP, and as an XMI file (XML Metadata Interchange, where XML stands for eXtended Markup Language). (# 3 in figure 1). < File: EHR-S_FM_R2IntermediateVersionSept29-2012/>
Tool design sheet. This describes the whole process (see figure 1 on the bottom of this report). This includes the UML metamodel (# 2 in figure 1). < File: Design Sheets from EA (2012-sep-26)/>

What has additionally been done till end of November 2012


Weekly Skype conference calls
Consultations of EHR WG members to obtain the Excel and XML source files of the EHR-S FM.
This wiki page for the project updated
Validation rules obtained from WG and put into a first draft document, for which input was asked in conference calls.
Checks against the XML to UML import meta-model for EHR-S FM R2 draft (v 3.2).
May 2012 XML from ballot was used as baseline file for the draft work.
90% ready UML representation of the EHR-S FM delivered.
Excel to XML exports developed
Decisions made to include the informative parts of the EHR-S FM as add on’s to the XML.
Preliminary work done for future export of the EHR-S FM from UML using MAX.
Initial testing approach discussed.
Export XML from Excel tool developed.
Import of EHR-S FM from new XML into EA now 97% ready.
Preview EHR-S FM Export in MAX developed.
First draft of user guide developed.

Deliverables of End November 2012


Report 3.
XML-GeneratorEHR-S FM R2 Zap. This file must be renamed to *.zip to open. It contains the Ruby tool to extract full EHR-S FM contents from Excel into XML. See the instruction in the user guide to install and apply.
EA file with the EHR-S FM fully included: EHR-S FM R2-XMLimport2.2Only.zap, to be renamed *.zip to allow extraction.
First preview of EHR-S FM export from EA: EHRS_FM_R2 (import v2.2) generated-ehrs-fm-20121115-full2.max
User Guide tool-v05.doc with the first draft for comment user guide, covering the part that has been prepared.

What has been done till end of January 2013

  1. Continued weekly Skype conference calls, with some interruptions for holiday and Jan WGM.
  2. A Github repository for the source code and all deliverables are made available for EHR WG.http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/
  3. MS Groove folder for internal use and meetings.
  4. PowerPoint presentations at HL7 Sept 2012 and January 2013 WGMs.
  5. Dependency discussed at WGM and in conference and individual calls.
  6. Mr. Corey Spears consulted in Dec 2012 and Jan 2013 with results in XML/ schema suggestions.
  7. EHR workgroup provided validation rules and reviewed the validation rules document.
  8. XML to UML import meta-model for EHR-S FM R2 draft was created (v 3.2).
  9. May 2012 XML was used as baseline file for the draft work.
  10. Corey Spears’ XML materials and Helen Stevens’ master Excel table where used to check and update the approach.
  11. 90% ready UML representation of the EHR-S FM delivered, waiting for update to 100% once validation is approved.
  12. Tool design sheet delivered, describing the whole process (see figure 1 on the bottom of this report).
  13. Excel to XML exports developed and delivered.
  14. Decisions made to include the informative parts of the EHR-S FM as add on’s to the XML.
  15. Export from EA EHR-S FM in UML to XML using MAX format confirmed, using xpath 1.
  16. Initial testing approach discussed and first draft test approach developed and delivered Jan 2013.
  17. Additional export XML from Excel tool developed and reviewed.
  18. Import of EHR-S FM from new XML into EA now 99% ready.
  19. User guide discussed with EHR WG, will be updated when new materials are approved.
  20. Errors in XML document has been discussed and solutions for most issues determined.
  21. Internal Testing the XML generation from XLS.
  22. Internal Testing Import of the full XML into EAP, using the XML R2 Schema.
  23. Organize feedback from WGs to UML representation of the EHR-S FM based on full XML export from Excel.
  24. Discuss the validation rules with WG and create first validator as stand alone version.

Summary of the January 2013 deliverables

  1. EHRSFM_EA_AddIn (2013-jan-27) v2.zap (http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/). This file must be renamed to *.zip to open. It contains the EHR-S FM extension to EA tool.
  2. FM-validation file.It contains the EHR-S FM validation tool in a version external to EA for stand alone testing.
  3. Unchanged EHR-S FM export from EA: EHRS_FM_R2 (import v2.2) generated-ehrs-fm-20121115-full2.max (http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/).
  4. Edit Forms in EA (2013-jan-27) which illustrates first drafts of the user interface for EHR S #FM (colored sections) and the validator output (black / white on left bottom). See figure below.
  5. EHR-S-FM-Testdesign. First draft for comment of the test of the tool by the EHR and tooling WG. the final document will be published.
  6. We have uploaded the release package to the GForge EHR-S FM Tool project here: http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/?action=index. This release is labeled 2013-Jan.

This release contains an update for the Enterprise Architect plug-in, a Schematron file to validate Functional Model extracts in MAX format, a stand-alone version of the Schematron file (an XSLT 1.0 file that will run with any XSLT 1.0 processor such as xsltproc on the command line), a sample MAX format file that contains an export of the preliminary load of the EHR-S FM into EA, a MAX format file that contains intentional error used in testing the Schematron validations, the validations document from the EHR WG with additional notes to trace the validation errors (by ID) to the source (not complete), the detail design spreadsheet containing the full list of validations identified to date with progress/status (and where applicable questions or comments on the validation), and a PDF with a sample of color-coding the input forms for the functional models in EA.

Please note that the Schematron validations and the detail validation design are preliminary deliverables, not final. We are expecting that these will continue to evolve in the next release cycle prior to final acceptance.

During EHR WG Conference cals the organization of the test will be discussed.

Sample of how sections, functions and criteria will look like in the EHR-S FM tool

Summary of the status March 25th 2013

During the EHR WG conference call on March the 19th, the project team gave a demo of the EHR-S FM Tool (draft). The following has been demonstrated:

  1. Install the EHR-S FM extension on a Windows PC
  2. Open the EHR-S FM .eap file in Enterprise Architect
  3. Browse and search in the EHR-S FM

The steps of these topics are summarized in the following PowerPoint presentation Demo_of_the_EHR-S_FM_Tool_19032013-v03.pdf. We agreed to put all the documentation on Gforce: http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/

Before you can use the tool and follow the steps as described in the PowerPoint presentation you must download and install the EHR-S FM Extension and the content of the EHR-S FM in an .eap file. The extension and the .eap file can be found on HL7 Gforce. Download these files and save them on your hard disk. For further steps see the PowerPoint presentation: EHR_S_FM_UserGuideManage_v02.zip

Along with the EHR-S FM Tool comes different chapters which are together the User Documentation. The following chapters are (in concept) available:

  1. Reader’s Guide: EHR_S_FM_TOOL_C0_Readme_v03 EHR_S_FM_TOOL_C0_Readme_v03.pdf‎
  2. Chapter One: Overview: EHR_S_FM_TOOL_C1_Overview_v02 EHR_S_FM_TOOL_C1_Overview_v02.pdf
  3. Chapter Two: Installing the extensions: EHR_S_FM_TOOL_C2_Installing the extensions_v02 EHR_S_FM_TOOL_C2_Installing the extensions_v03.pdf
  4. Chapter three: Import & Export: this chapter is not ready for publication yet.
  5. Chapter Four: Manage: EHR_S_FM_TOOL_C4_Manage_v03 EHR_S_FM_TOOL_C4_Manage_v03.pdf
  6. PowerPoint presentation with instructions: EHR_S_FM_UserGuideManage_v02 EHR_S_FM_UserGuideManage_v02.zip

Note 1: all the files will be on Gforce. Maybe there are not there yet, but they will be very soon.The version of the files can be different than mentioned here, because we are continue updating them.

Note 2: the use of the EHR-S FM Tool to make a Functional Profile is out of scope in phase 1.

Summary of the status April 9th 2013

  1. We imported the EHR-S FM R2 of the May ballot 2013 in the EHR-S FM Tool.
  2. We updated the EHR-S FM Meta model. This is in the Overview Chapter.
  3. We still need to complete the html rendering. We need to compleet CSS for that.
  4. We still need to do Formatted Object generation to create the pdfs.
  5. We need to do minor adjustments, so a new msi file will be created.

Note: by the end of this week all documents, the eap file and the msi file can be found at GForce: http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/

Final deliverable phase 1 May 2013

This summary describes the final deliverables for this phase 1 work on the creation of tooling for the EHR-S FM. The deliverables are listed in the table below. However, all the files you can find on GForce: http://gforge.hl7.org/gf/project/ehrsfm_profile/frs/

Deliverable File Description File Names Content
User guide Reader’s Guide EHR_S_FM_TOOL_C0_Readme.pdf Description of the EHR-S FM Tool Release 1 package content and files.
User guide Chapter One: Overview EHR_S_FM_TOOL_C1_Overview.pdf Background. Purpose & Scope.

Overview and Design of the EHR-S FM. Tool. Anticipated Uses.

User guide Chapter Two: Installing the extensions EHR_S_FM_TOOL_C2_Installing the extension.pdf Description of the import of the EHR-S FM in the Tool. Description how to handle the Enterprise Architect extension.
User guide Chapter Three: Import & Export EHR_S_FM_TOOL_C3_Import&Export.pdf Description of how to import the EHR-S FM XML and the MAX file. Description of how to export the EHR-S FM from the Tool into MAX format
User guide Chapter Four: Manage EHR_S_FM_TOOL_C4_Manage.pdf Description of how to manage the components of the EHR-S FM.
User guide Chapter Five: Ballot EHR_S_FM_TOOL_C5_Ballot.pdf Description of how to use the EHR-S FM tool for ballot purposes.
User guide PowerPoint presentation with instructions EHR_S_FM_UserGuideManage.pdf Print screens with instructions of how to work with the EHR-S FM Tool.
EHR-S FM in EA Enterprise Architect explanation file with EHR-S FM in UML Design Sheets from EA (2013-May-24)v5.pdf. EHR-S FM Tooling Design.eap This pdf file contains the following UML

diagrams: EHR-S FM R2 spreadsheet to XML schema. Mapping of EHR-S FM R2 XML schema to UML Meta Model. UML Meta Model 3.4 EHR-S FM R2. UML representation of EHR-S FM, first draft. Glossary mapping. The files are developed in a separate EA file which has these diagrams in design mode.

Validation Validation rules spreadsheet with rules used to develop the EHR-S FM tool ValidationRulesEHR-SFMR2-20130520-AS.xls Description of all the validation rules that are used to develop the validation process
Publication EHR-S FM R2 export in MAX format EHRS_FM_R2 (import v2013-mar-29)-full.max An export of the EHR-S FM R2 in MAX format. The import refers to the May 2013 ballot master spreadsheet that is the basis for this.
Extra XML Generator for EHR-S FM spreadsheet EHR-S FM_R2_XML-Generator.zip (named .zap, rename to .zip to extract) During the creation process of the EHR-S FM Tool, the project team encountered some issues with the existing XML file from the May 2012 ballot. This was the reason to create a standalone tool that allows generating a full XML file from the Excel spreadsheet for EHR-S FM.
EHR-S FM in EA EHR-S FM Extension EHRSFM_EA_Extension.Setup (2013-may-27).msi or EHRSFM_EA_Extension.Setup (2013-may-27).RENAME_to_msi The EHR-S FM Extension to EA as an .msi file. This is the tool. Some websites do not allow storage as .msi, so it is often .RENAME_TO_msi.
EHR-S FM in EA EHR-S FM Content for Enterprise Architect EHR-S FM R2 (@GForge v2).eap The EHR-S FM content in a for Enterprise Architect readable file (eap file). This is a ready to go file, preventing that every user should import the full.max file themselves.
Publication XSLT for MAX to HTML max2html.xsl, functional-model.css, functional-model.scss, ehr-s-fm-ballot.mif XSLT stylesheet for the html publication of the EHR-S FM export in MAX output from EA. With Cascading Style Sheet and SCSS source file for it. The ballot MIF file adds the ballot details, cochairs and copyright statements to the html and pdf publication.
Publication XSLT from MAX to FO to PDF max2fo.xslt, ehr-s-fm-ballot.mif, EHR-S-FM_R2-rom-max.pdf An XSLT stylesheet that allows the conversion of the html to FO and from there into PDF. The MIF contains the ballot details. The pdf with the browsable content list is the result.
Validation Validation testing of EHR-S FM via XML artifacts fm-max-validation-test.xml, FM-validation.sch, fm-validation.xslt, Validation output (2013-apr-18).txt Set of files that validate the FM using the MAX export and external validator. The validation report is send back to the user in the EA interface. The txt document is an example of output. Every rule is tested with a pass / fail result.
All tooling parts Source code for the EHR-S FM Extension HL7 SourceCodeEHR-S FM Tool (2013-may-27).zip This contains the visual studio 2010 C# source code for the solutions and the projects. And the MAX materials.
Publication Publication documents generated from the EHR-S FM tooling output in html and pdf EHR-S-FM_R2-from-max.html, EHR-S-FM_R2-from-max.pdf The EHR-S FM in a html format generated from the MAX export coming from Enterprise Architect. It uses a Cascading Style Sheet. The Excel is a simple open the XML file. This creates a 35375 line long Excel.

Phase 2 September 2013

Phase 2 is started, the contract is finalized. So we continue working on the EHR-S FM Tool according to the PSS. This PSS was accepted and distributed in the EHR WG. We are working on the first deliverable as presented in the conference call of September the 10th. this first deliverable is a Requirements analysis (Deadline September 30th). An analysis of the How to Profile guide and the Conformance Clause was carried out (need to update with the new document for the ISO ballot). From there we are developing Use Cases, Activity diagrams and Requirements. A first presentation and discussion of this was presented in the conference call. Next week there will be a follow up. Some examples: Note: this is work in progress, so CONCEPT!

Upcoming HL7 WGM in Cambridge On Monday Q4 we will give a demo of the EHR-S FM Tool, the status as it is now. Also will we give an introduction into phase 2 of the Tooling project. We want to have a discussion on the requirements, maybe in a focus group during the week. In this way we can make the deadline of September 30th.

Questions asked and activities for us:

  1. Requirements for combining, merging and comparing profiles.
  2. How to assign parts of the functional profile to different people? Export as xmi file, make an .eap file? It is possible to split the work.
  3. How to use the tool to capture feedback?
  4. Developing the tool there will be different roles: a reviewer who can read only the profile (or a part of the profile) and add comment in a comment section. Another role is the editor role who can make the actual changes in the functional profile.
  5. It will be important to track and trace changes in the profile.
  6. there are novice and expert users. For the novice user it might be best to have default settings that makes it easy to profile.Creating a Toolbox sounds great.
  7. How to use the Glossary in the creation of a profile? The EHR-S FM Glossary stays as it is. An update will always be done by a ballot process. If the profile uses new terms than there will be a kind of extension of the original glossary. In an update of the original glossary there will be a review of the extensions. How to make and handle an extension?
  8. How to update the glossary after a ballot?
  9. Do we need a running server for Team Review in EA (question of Stephen)? Not necessary, but role base access should be handled on file level? How to deal with this?

We continue working. Michael reviewed the work of Anneke on Friday September the 13th. This file is the first draft which will be discussed Tuesday 17th September in the conference call and finalized during the WGM. Add a new file on Monday the 16th of September in the afternoon (Our time). Differences are:

  1. Changed the High Level Use Cases;
  2. Added the following Use Cases, Activity diagrams and Requirements: Profile Combining, Profile Comparing, Profile Merging, Profile Views.
  3. Not done yet, needs discussion: Profile Balloting and Profile Rendering.
  4. Deleted working in a Team: is a functionality of EA. If someone wants to use that in the process of Profiling, this is possible.

Phase 2 Work-In-Progress Artifacts

All WIP artifacts can be found here: https://app.box.com/s/938b1c1wuprl52nbpazk

These include:

  1. Enterprise Architect Tool Phase 2 Design file (EAP)
  2. Generated Document from the Design (RTF/DOC)
  3. Validation Rules (XLS)
  4. Questions for the EHR WG

Phase 2 Deliverables

It is December the 3th and almost the end of 2013. This description is to give you an update of phase 2 of the EHR-S Tooling project. The project team worked together with the EHR WG on the deliverables described in the PSS. Last Friday, November the 29th we had a meeting as a project team and discussed how to actually build the profiling tool and how the steps in Enterprise would look like. We made a presentation with mockups and published this on Box (the link you can find in Phase 2 Work-in-progress Artifacts.

The deliverables until now are; 1. The requirements (deliverable 1 in the PSS): this is approved by both the EHR WG and the Tooling WG. 2. Validation Rules (deliverable 2 in the PSS): this is approved by both the EHR WG and the Tooling WG. 3. The types of profiles (deliverable 3 in the PSS): this is apporved by both the EHR WG and the Tooling WG. 4. Profile Views (deliverable 4 in the PSS): this is approved by the EHR WG.

All the deliverables can be found on GForge http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/

Phase 2 Update April 3th 2014

We are busy to implement the requirements that are needed for the creation of a FP with support of the tool. The two examples that we are using for this implementation are RM_ES FP and the MU FP. Both eap files are on box; https://app.box.com/s/938b1c1wuprl52nbpazk If you install the latest version of the extension, HL7_FM_EA_Extension 20140328-4.msi, you can open the eap file and look at the model of the FP's. If you want you can play with this.

How to install the extension is described in EHR_S_FM_TOOL_C2_Installing the extension_v01.pdf

You will also find some content for the learning center in EA; https://app.box.com/s/oetxahgb9k4emgveaodh For now these are pdf documents you can consult for working with the tool at this moment. Before the end of April we will include them in the learning center of EA.

NOTE: we asked for an extension on the deliverable date (of March 31th) and the WG agreed with this.

Phase 2 Update May 12th 2014

All the basic requirements for the development of a functional Profile are implemented in the EHR-S FM Profiling Tool. The latest version of the msi extension is HL7_FM_EA_Extension 20140429. The RMES FP and the MU FP were used to implement the requirements and to test the tool. As always work in progress can be found on box: https://app.box.com/s/938b1c1wuprl52nbpazk Meanwhile we delivered the next deliverables to HL7 International after approval by both the EHR WG and Tooling WG. These deliverables can be found on GForge (after you logged in): http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/Phase2Deliverables6/

At this stage the tool can be used to develop a new Functional Profile based on the EHR-S FM R2.0. How to use the tool for that can be found in the user guides also on GForge, but also in the Learning Center in EA (can be consulted after installing the extension). However, the tool is still in development, so changes will be made in the upcoming weeks. Changes are improvement of the implementations in the tool, it can happen that there are still bugs in the tool. These improvements will not effect your work. Other changes concerns further implementation of the requirements. We are working on the requirements for combine, compare and merge functionalities. Use case for this is the PHFP. These further implementations will not effect your work.

If you want to use the tool for the development of your functional profile please contact the EHR WG and we can plan a meeting in where we can give you instructions in how to start using the tool.

Phase 2 Update September 22th 2014

As described in the May update all the basic requirements for the development of a Functional Profile were implemented in the EHR-S FM Profiling Tool. Four significant steps were made since then: 1. The Meaningful Use Functional Profile (MU FP) was created for the August 2014 ballot. 2. HL7 Italy uses the tool for the creation of their Realm Functional Profile. 3. The publication tools and format were developed and used to publish the MU FP and the EHR-S FM for ISO. 4. Started the implementation of the Combine, Compare and Merge functionality.

Several issues on the tool and on the rules of creating Functional Profiles were detected while working on the MU FP. All issues detected were included in GForge and fixed in the tool. Also HL7 Italy detected these issues and had issues in the context of using the tool for the development of a Realm Functional Profile. The last ones will be addresses in phase 3 of the tooling project.

The publication format, tools for that and the steps of how to create a publication were developed and used. A final user guide will be available on Box soon: https://app.box.com/s/v4so451jerv1xicshyox

For the Combine, Compare and Merge functionality we discussed the requirements and a mockup based on this requirements with the Public Health Functional Profile team. A first (partly) implementation was discussed in the regular EHR WG conference call and showed during the WGM in Chicago. The current implementation status and the direction to finish it were approved by the EHR WG.

Also the user guides were updated and included in the EA Learning Center and uploaded to box: https://app.box.com/s/oetxahgb9k4emgveaodh . A tutorial presentation was created and used for the hands on sessions during the HL7 WGM in Chicago.

In the hands-on sessions there were some problems with the tool. One of the problems was related to version 11 of Enterprise Architect (EA). Some participants had this version installed and couldn’t see the costumed learning center and toolbox. However, some had no problems with that. We will investigate what the reason for this is. Some participants worked with the trail version of EA. Working with this version is not a problem, but saving the work is not possible. For the tutorial in January 2015 we will come up with some pre-requisites because of the experiences from the hands-on sessions.

As described before, all work in progress can be found on Box: https://app.box.com/s/938b1c1wuprl52nbpazk. The latest version of the msi extension is HL7_FM_EA_Extension v2.14.0915. Also the user guides can be found on Box: https://app.box.com/s/oetxahgb9k4emgveaodh

If you want to use the tool for the development of your functional profile please contact the co-chairs of the EHR WG.

Phase 2 Update End October 2014

In the EHR WG conference call the following motions were approved:

Motion 1. Electronic Health Record Workgroup is asked to accept an extension of 4 weeks for deliverable 12. Combine, Compare, Merge. Additional guidance and tool formatting to support profiling tasks such as comparing profiles, comparing functions, merging functions and criteria from separate profiles. The Results 4 Care team used a mock up design and had further discussions with EHR WG members for the functional requirements. The work is significant more difficult than anticipated. We are making progress, but might not make the deadline of Oct 31. The EHR WG approved an extension of one month (November the 30th) to finish the implementation of the combine, compare and merge functionality.

Motion 2. Electronic Health Record Workgroup is asked to accept deliverable 10: support the work process of profile creators.


Motion 3. Electronic Health Record Workgroup is asked to accept deliverable 11: Publication artifacts for EHR-S FM profiles using HL7 MAX approach.


Motion 4. Electronic Health Record Workgroup is asked to accept deliverable 14. Update reports and wiki contributions.


Motion 5. Electronic Health Record Workgroup is asked to accept deliverable 16. Tutorial presentation (i.e. pptx) for the profiling tool.


Motion 6. Electronic Health Record Workgroup is asked to accept deliverable 17. Provide initial support to key WG users in installing and initial use of tool.

See for more detail the minutes of the EHR-WG conference call.

In order to store all the materials of the EHR-S FM FP Designer Tool Results 4 Care proposed to develop a webpage which can be placed behind the member login of the HL7.org website. On this site the user guides and software can be stored and obtained by HL7 members. An example webpage was developed based on the FHIR webpage of HL7 International. How, by whom etc. will be discussed with HL7 headquarters.

In the meantime all the final materials can be obtained by contacting the EHR WG co-chairs: http://wiki.hl7.org/index.php?title=EHR_Leadership Note: Box is no longer up to date with the latest materials.

Requirements for webpage to store EHR-S FM artifacts November 2014

The purpose of this webpage is to store artifacts in the context of the EHR-S FM FP Designer tool. So it is not the purpose to store the HL7 standard itself, but files the user need to use the tool.

For the development of the webpage requirements are needed. We will collect the requirements on this wiki during the discussion about the requirements.


Requirements are:

  • Provide the user interface to:
    • the extension/ the EHR-S FM FP Designer tool.
    • the installation guide of how to install the Extension.
    • the user guides of how to use the tool.
    • the max file of the EHR-S FM R2, latest version.
    • the max files, Profile Definition and Compiled Profile of the Functional Profiles.
    • the eap file of the EHR-S FM R2, latest version.
    • updates on the extension and user guides.
    • a Forum in where users can discuss the functionalities of the tool and/or their experiences with the tool.
    • history of the development progress of the extension.


Phase 2 Update December 2014

Phase two of the EHR-S FM Profile Designer tool has ended. All the deliverables were delivered in time. In the conference call of the EHR WG the following motions were approved.

'Motion 1.' Electronic Health Record (EHR) Workgroup and Electronic Services and Tools (EST) Workgroup are asked to accept deliverable 12. Combine, Compare, Merge of the Profile Designer Tool. Additional guidance and tool formatting to support profiling tasks such as comparing profiles, comparing functions, merging functions and criteria from separate profiles. The Results 4 Care team used a mock up design and had further discussions with EHR WG members for the functional requirements. The work took significant more time and energy than anticipated. However, through breaking it down in smaller steps it became possible to continue the work and achieve a working system allowing handling both mergers on profile level, and on individual criteria, based on a component illustrating the differences between profiles. The current set of comparable profiles in one session is 3, which is one more than the required 2 according the original plan for phase 2. It is still possible to combine more through iteration of the process. The msi file containing this functionality is placed in EHR co-chair Dropbox and in Gforge. The materials are available at http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/FinalDeliverablePhase2/ Please note that some validation files and source code materials are in the SVN.

Motion 2. Electronic Health Record Workgroup and Electronic Services and Tools (EST) Workgroup are asked to accept deliverable 13: Final testing of all tool components of the Profile Designer Tool. The deliverables 1 – 12 will be tested by the EHR and the Tooling workgroup. The EHR WG has been testing the tool through the actual development of FM ballots and FP ballots. These can be seen as acceptance testing of the overall functionality. Many issues and bugs were reported and have been handled by the R4C team. Further, we have created a unit test, and tested the various components. A set of test reports is available. The final test report is placed in EHR co-chair Dropbox and in Gforge. The materials are available at http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/FinalDeliverablePhase2/

Motion 3. Electronic Health Record Workgroup and Electronic Services and Tools (EST) Workgroup are asked to accept deliverable 15. Final User Guide set for profiling using the Profile Designer Tool. The R4C team created a range of user guides, one for each significant step in the whole process from starting a project to finalizing the publication. Each user guide has been reviewed by EHR WG members and many have been used during the various demonstrations, workshops, and other events. The set is ready and delivered to the co-chairs due to the copyright arrangements. The last one is about the combine, compare and merge functionality and handed in together with the new tool version that includes this functionality. In addition, R4C created a learning center for the tool using basic EA functionality, and stored the user guides on our server. We created a website with the recent FHIR look and feel to allow HL7 to place both the access page to the learning center plus all user guides and other documentation behind the secure site for members only. HL7 is currently working on the final publication site for members only. The user guide and documentation set is placed in the EHR co-chair Dropbox and Gforge The materials are available at http://gforge.hl7.org/gf/project/ehrsfm_profile/docman/FinalDeliverablePhase2/

We still need approval of the EST WG.

Past Activities

  1. Creation of an EHR Tooling list - Helen
  2. Invite Profiling SMEs - John
  3. EHR-S FM Chapter 2 -> Link ???

Current Functional List

The following list contains all thus far identified functionality in general order of priority (greatest to least)

Input (not specific to this project, but defined through from EHR-S FM development and publication)

  • EHR-S FM R2 source in XML


Absolute Functionality (Top Priority)

  1. Enforce profiling rules (per Conformance Chapter)
    1. Include/Exclude functions from profile
    2. Conformance Optionality
    3. Conditional Criteria
    4. Criteria Inheritance
    5. Add functions and criteria
    6. Modify functions and criteria
    7. ... (Other absolute profile rules)
  2. output formats
    1. HTML
    2. PDF
    3. XML
  3. Browse & Navigation of the funtional model
    1. search capabilities, filtering capabilities, keyword search, search & replace.
  4. Tool is framework specific (e.g. coded to EHR WG FM framework specifications), but content in-specific (enables the import/export of different conformant models/versions (e.g. EHR-S FM 2, future PHR-S FM). (Tool is content agnostic)
  5. Save profile

Needed Functionality (High priority)

  1. Ability to revert to previous state (undo)
  2. Simple text copy paste (text editor related)
  3. Text formatting (highlight, bold, underline, font, italicize
  4. Show dependencies between functions/criteria
    1. Show impact of changes
  5. Undo changes
  6. Capture comments regarding specific elements (i.e. comments regarding specific functions or criteria)
  7. Initialize/revert to conformant base standard (clear old comments, reset to clean restart to new version activity)
  8. Ability to link functional model/profile (intra/inter base standard and profile, linked to a conceptual model, bi-directionally)


Operative Functionality (Medium Priority)

  1. Output format HL7 HTML publication format (i.e. to publish through HL7 Publishing)
    1. Generate publication ready documents.
  2. Attach front-matter to publication. Chapter 1 (Additional material
  3. Maintain original for comparison with modified function/criteria
  4. Compare to other profiles
  5. Merge Functions/Criteria from separate Profiles
  6. Export Sections from Master or working copy
  7. Function copy paste
  8. Balloting & reconciliation traceability version control
    1. Managing voting and input from reviewers.
    2. Reporting out all comments against an element.
  9. Capturing institutional memory "allow for comments/notes" attached to elements.
  10. converting a profile from one version to the next.
    1. If you have a profile based on R2.0, have the tool update baseline profile to R2.1 as starting point.
  11. Requirements regarding tooling access (online)
    1. Support multi user - multiple users working on same profile at same time?
    2. User Management, access control
  12. Workflow management tool (assigning activities to users)


Additional Functionality (Low Priority)

  1. mobile access
  • Note - will not support R1.1. Is it necessary to convert R1/R1.1 to R2?

Listserv

The EHR-S FM Profiling Tool Project is currently being set up.
To subscribe to a list service, please go to the HL7 Listservices Welcome Page

Additional Work

Make the FM available in UML for incorporation in UML Modeling & Design. Used with the EHR FIM, see EHR Interoperability WG. The mapping is for R2 now as work in progress for the EHR-S FM tool part phase 1. See first picture below. An earlier version for R1.1. has informed the work for R2. See 2nd picture below.

R2 Meta model in UML work in progress




R1.1 UML meta model