The modern hospital information reform in OA Office collaboration platform design (1)

This article from the hospital administration management perspective, introduced the modern hospital in information reform process, the collaborative platform of OA office design principles and system framework.

In this article, the hospital Office collaboration platform is divided into general categories of functional components and special classes, and on the main functional components, such as approving management, schedule management, human resources management are described and some important technical point.

I. introduction

Construction of hospital OA has undergone several stages, from manual documents into electronic documents, to the Administrative Office of the information in the automation process, to the personnel system, the official document system, file system, and gradually established.

But these systems design and development process, often considered a single functional business and needs, a single workflow features and functionality. Today, the hospital management has evolved from previous results management to process management, from extensive management to fine management of change. Administrative Office is becoming more and more attention to sectors and departments, departments and collaboration among employees. Through information sharing technology, communication technology to strengthen the sector and communication between employees, improve office efficiency.

Ruijin hospital is a three-level class a large comprehensive teaching hospital.

Currently, Ruijin hospital information system from the two systems-management control systems and decision support system, developed for medical procedures, medical equipment, medical services, hospital management and medical resource sharing five digital platform, for a total of 284 44 system, a subsystem. Where the Office collaboration platform for hospital management platform, an important part, have achieved certain results.

Second, the hospital, in collaboration with the Office platform construction principle

-Object-oriented application framework

Clear platform service object, from a user perspective, understanding of the needs of clients, demand-oriented, the user needs design platform application.

-Service-oriented technology framework

The technology framework to emerge from the original on the dispersion and independent services to a single user mode.

Use SOA service-oriented approach to application design, extract common service content, reduce duplication of effort.

-Humanist website framework

Platform framework priority in accordance with the amount of access and content of priority determine the channel sections of exposure, and gives the user a custom personalized navigation interface.

III. system framework

Map: OA Office Ruijin hospital collaborative platform framework

As can be seen from the figure, Ruijin hospital information system is mainly divided into clinical diagnosis and treatment of HIS oriented and PACs systems, as well as for internal management and external services of the portal system.

The regional information sharing platform as an external system exchange data carrier, only to HIS system provides regional medical resource information exchange, this article does not describe. Ruijin hospital information system in the Office, in collaboration with the platform is the main discussion of this article.

OA Office Ruijin hospital collaborative platform (hereinafter referred to as platform) are divided into platform application and platform services layer.

Platform application layer various Office applications through a single sign-on (SSO), and other technical means and the hospital intranet portal has been integrated. And platform services layer is platform application layer offers a wide range of data exchange, security, authentication, authorization and workflow services support.

Fourth, the main function of the platform services layer

Platform services layer for the upper platform application layer provides the data source, authorization, workflow, Exchange integration services is a platform for the application-tier infrastructure.

Platform service layer using SOA technology architecture, service oriented design perspective. In addition to the platform to support the application layer, you can be Ruijin hospital information system for the use of other modules.

1. data source

In this platform for all data in a unified data object in the form of management, and provide data access services.

To schedule management, for example, in schedule management sector schedule management, staff need to create a schedule, the schedule management need to be aware of the employee's Department of information. Past practice, one is in schedule management data stored in the storage of information, staff, departments and employees in human resources management department information to synchronize, the second is directly read human resources information systems staff departments. The first approach, would increase the system's complexity and redundancy of data, additional overhead to ensure data consistency; the second approach is an application of physical storage directly opened to other systems, in the event of a change in the physical data storage, and related systems are needed to modify that flexibility is not enough.

Using the data source, all the data in a unified data object to display the data in isolated storage, significantly reducing data redundancy, regardless of data consistency issues, and the service interface in the data source does not change the physical data structure changes, will not have an impact on other applications.

2. authorized service

The platform for all applications provide uniform licensing and certification services.

Authorized services is the core roles, each user has at least one role, each role is defined you can access the resource. Resources can be data, the application interface or an operation, etc. For example, a workflow service, define the workflow, a workflow node can be assigned to a role, instead of a specific user. This limits the unauthorized user to access workflow resources and increases the flexibility of workflow execution, you can pass on the role of a user authorized to control the flow of the workflow.

3. workflow services