EPR-eFolder(Workflow) - EPR-forum goal is Bridging Information Systems in Real Time !

NEWS
• BI Seminars: eHealth SINT 2013-2017
• BI Seminar WS1: Ledelsesparadigme i Kommunal Helsetjeneste
• Our Contribution to the IEEE Digital Ecology Conference 2013 24-26th July
• OASIS has now approved Transformational Government Framework (TGF) as a new OASIS standard
• CAM editor tool an EU Joinup project
• OASIS Applauds European Union’s Reform Embracing Broader Cooperation with Open Standards Consortia
• New EPR-forum webpage with focus on -Services in Your hand-
• Blogg input to the Norwegian Minister of Health
• Webinar: eGov as a common superstructure platform
• EPR-forum contribution to public hearing on 'Healthcare Innovation'
• NIEM and Oracle
• Oracle now part of the OASIS CAM templating work !

EPR-eFolder standard:
( Service management part)
One obvious solution will be to extract the computer support into electronic folders. The folders will have a standard design with standardized functionality when functions are generic. The folders will give the user access to all needed information and help in the performance of the task. Access will given through "single sign on" and approved digital signatures for identification. Special applications and expert systems will be integrated into the folders. A draft for a general functional standard in order to structure and organize the content in the folders has been developed.

Important properties of the folders are:

The folders are a framework. The framework has several purposes, a common access point for all relevant information, in order to integrate under laying systems, to be used as next generation of «front Office". The framework will function by use of open standards for processing witch are XML-based templates. The folders will also be able to use a number of other standards.
Integration of applications and data will be controlled by commands (on demand). Applications can be components in special applications, expert systems, help for users e.g. Access on command is the opposite to permanent access. Access on command belongs to a technology called «loosely coupled applications».
The folders are customized (adapted) for the actual need. This means that only correct and needed information will be available through the folders.
The folders are dynamic, they can be extended or reduced as needed. This is possible because of the standardized structure that the folders have been designed around. The structure is the base for «automatic» modeling of generic information.

The principles around customized folders and access on command are important components in order to avoid unnecessary dispersion of information. In addition to clear role structure this is especially important in order to protect sensitive information and to protect personal integrity.

These properties are basic prerequisites in order to develop dynamic solutions through Service Oriented Architecture (SOA). SOA represents a major shift within IT architecture. SOA with attached technology is necessary if integration and interoperability between systems shall be able to fully realize. A prerequisite for SOA is that traffic rules exist. Traffic rules will secure cooperation between the necessary framework and the underlying system that shall be integrated. The rules has to be standardized and used in practice. It will be a big advantage (and probably necessary) if the authorities take responsibility to establish the traffic rules.

It is our believe that the standardizing that e-Folder represents will contribute to make SOA to a success. The most obvious reasons are that the structure in e-Folder represents abstractions (1) that will be the foundation to generate templates that can be used to process underlying systems from the framework (2). Many of the international standards that are needed in order to realize SOA will be used. These are standards supported and promoted by Microsoft, IBM, HP, Sun e.g.

An understandable example: Still today the oil companies are struggling to establish cooperation between norms within the technical specifications in the engineering, construction and production phase of an oil platform. Each of the actors are still using proprietary solutions. The result is both costly and resource demanding work in order to handle the norms that is necessary to run a normal business production.

The same situation is also true for governmental supervision authorities and businesses, and between other organizations that produce rules and restrictions for the same businesses. If they were all based on the same foundation that is framework with a common structure and basic functionality it should be possible reach a common goal. The demands of the community on quality and traceability within the various supervision areas have to be met.One obvious solution will be to "pack" the computer support into electronic folders. The folders will have a standard design with standardized functionality when functions are generic. The folders will give the user access to all needed information and help in the performance of the task. Access will given through "single sign on" and approved digital signatures for identification. Special applications and expert systems will be integrated into the folders. A draft for a general functional standard in order to structure and organize the content in the folders has been developed.

-------------------------------------------------------------------

EPR eFolder standard in Healthcare:

See also the project "70+ Elderly Care Challenges"

Through a neutral and public defined SUPER STRUCTURE we want to demonstrate how to solve much of the rising Healthcare interaction problems related to the upcoming elderly wave.
We want to show how a "real" open SOA based Super structure portal are processing eFolder scenario based TEMPLATES. An infrastructure of XML methods specified by the OASIS BCM and CAM standards dealing with real time software modeling and processing in real time. The SOA portal is interacting with under lying legacy and expert systems by orchestrating and administrating loosely coupled applications (Web services and ebXML) .

EPR-eFolder Templates:

An eFolder Management Template goes through 3 phases:

1. Construction and Certification( Template Class ) Role 1

2. Composing (Template Object, serialisation) Role 3 & 4

3. Sheduling ( Template processing in an eFolder Engine ) Role 3 & 4

These 3 phases needs different skill as illustrated in this figure:

Courses in these topics held by IT&Integration AS