Medical system and authority management method thereof
By introducing permission management methods in the medical system, using the first-level administrator to set up the second-level administrator and assign permissions, the management complexity and operation and maintenance burden of the medical system in group management is solved, and flexible management is achieved and efficient operation and maintenance.
Patent Information
- Application Number
- CN202010953741.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-09-11
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-09-11
AI Technical Summary
The existing medical system has weak support for group management, resulting in more cumbersome management of large and medium-sized medical institutions, increasing operation and maintenance work, and unable to issue functions, limiting the flexibility of organizational structure and authority management.
Provide a method of permission management in the medical system, set up roles through the first-level administrator, establish a second-level administrator, and assign menu, function and data access permissions to them, support organizational structure and department maintenance, and realize the dynamics of menu functions. Configuration, adapt to the permission settings of different roles, and reduce the operation and maintenance burden.
It realizes flexible management of medical groups and hospitals, reduces the operation and maintenance work burden, improves management efficiency, supports diversified permission settings and organizational structure adjustments, and ensures the scalability and convenience of the system.
Smart Images

Figure CN112100658B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of medical system management, and in particular to a medical system and a method for managing rights thereof. Background Art
[0002] Medical system is a frontier science that integrates medicine, information, management, computer and other disciplines, and has been widely used. Medical system is the necessary technical support and infrastructure for the operation of modern hospitals. The purpose of realizing medical system is to strengthen the management of hospitals, improve the work efficiency of hospitals and improve the quality of medical care by more modern, scientific and standardized means. Summary of the invention
[0003] According to one aspect of an embodiment of the present disclosure, a method for authority management of a medical system is provided, comprising: in response to a role setting operation of a first-level administrator corresponding to a medical group layer, establishing a second-level administrator for a hospital, and assigning corresponding menu, function and data access rights to the second-level administrator, wherein the hospital is a subordinate institution of the medical group layer; and in response to the role setting operation of the second-level administrator, assigning menu, function and data access rights corresponding to the user to the user.
[0004] In some embodiments, the hospital includes: a first hospital and a second hospital different from the first hospital, and the second-level administrator includes: a first administrator and a second administrator different from the first administrator, wherein the menu, function and data access rights corresponding to the first administrator are different from the menu, function and data access rights corresponding to the second administrator.
[0005] In some embodiments, the users include: a first user and a second user different from the first user, wherein menu, function and data access permissions corresponding to the first user are different from menu, function and data access permissions corresponding to the second user.
[0006] In some embodiments, the permission management method further includes: adding, deleting or modifying organizational structure information in the medical system in response to the organizational maintenance operation of the first-level administrator.
[0007] In some embodiments, the authority management method further includes: adding, deleting or modifying department information in the hospital's architecture in response to the department maintenance operation of the second-level administrator.
[0008] In some embodiments, the permission management method further includes: configuring administrator information of the second-level administrator in response to the information configuration operation of the first-level administrator; and configuring user information of the user in response to the information configuration operation of the second-level administrator.
[0009] In some embodiments, the permission management method further includes: in response to the menu setting operation of the first-level administrator, configuring multiple menu functions, wherein each menu function corresponds to a role identification of at least one of the first-level administrator, the second-level administrator and the user.
[0010] In some embodiments, the organizational structure information is in the form of a tree menu, and the organizational structure information includes regions and hospitals; wherein the region includes subcategories, and the subcategories include the hospital or the next-level region, and the hospital is the last-level node of the organizational structure information.
[0011] In some embodiments, the authority management method also includes: in the process of modifying the organizational structure information, modifying the parent organization corresponding to the currently adjusted organization, and ensuring that the address identifier of the currently adjusted organization remains unchanged, wherein the historical medical data of the currently adjusted organization is stored in the address identifier.
[0012] According to another aspect of an embodiment of the present disclosure, a medical system is provided, including: a receiving module for receiving a role setting operation of a first-level administrator corresponding to a medical group layer or a role setting operation of a second-level administrator corresponding to a hospital, wherein the hospital is a subordinate institution of the medical group layer; and a role management module for establishing a second-level administrator for the hospital in response to the role setting operation of the first-level administrator, and assigning corresponding menu, function and data access rights to the second-level administrator, and assigning menu, function and data access rights corresponding to the user to the user in response to the role setting operation of the second-level administrator.
[0013] In some embodiments, the medical system further includes: an organization management module, configured to add, delete or modify organizational structure information in the medical system in response to the organization maintenance operation of the first-level administrator.
[0014] In some embodiments, the medical system further includes: a department management module for adding, deleting or modifying department information in the hospital architecture in response to the department maintenance operation of the second-level administrator.
[0015] In some embodiments, the medical system further includes: a user management module for configuring the administrator information of the second-level administrator in response to the information configuration operation of the first-level administrator, and configuring the user information of the user in response to the information configuration operation of the second-level administrator.
[0016] In some embodiments, the medical system also includes: a menu management module, used to configure multiple menu functions in response to the menu setting operation of the first-level administrator, wherein each menu function corresponds to a role identifier of at least one of the first-level administrator, the second-level administrator and the user.
[0017] According to another aspect of an embodiment of the present disclosure, a medical system is provided, including: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the aforementioned method based on instructions stored in the memory.
[0018] According to another aspect of the embodiments of the present disclosure, a non-transitory computer-readable storage medium is provided, on which computer program instructions are stored. When the instructions are executed by a processor, the method described above is implemented.
[0019] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0021] The present disclosure may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:
[0022] Figure 1 is a flowchart showing a method for managing rights in a medical system according to an embodiment of the present disclosure;
[0023] Figure 2 is a flowchart showing a method for managing permissions for a first-level administrator of a medical system according to an embodiment of the present disclosure;
[0024] Figure 3 is a flowchart showing a method for managing permissions for a second-level administrator of a medical system according to an embodiment of the present disclosure;
[0025] Figure 4 is a flowchart showing a method for managing rights in a medical system according to another embodiment of the present disclosure;
[0026] Figure 5 is a schematic diagram showing the structure of a medical system according to an embodiment of the present disclosure;
[0027] Figure 6 is a schematic structural diagram showing a medical system according to another embodiment of the present disclosure;
[0028] Figure 7 is a schematic structural diagram showing a medical system according to another embodiment of the present disclosure;
[0029] Figure 8 is a schematic structural diagram showing a medical system according to another embodiment of the present disclosure;
[0030] Fig. 9 is a schematic diagram showing an organization management interface of a medical system according to an embodiment of the present disclosure;
[0031] Fig.10 is a schematic diagram showing a department management interface of a medical system according to an embodiment of the present disclosure;
[0032] Fig.11 is a schematic diagram showing a role management interface of a medical system according to an embodiment of the present disclosure;
[0033] Fig.12 is a schematic diagram showing a user management interface of a medical system according to an embodiment of the present disclosure;
[0034] Fig.13 is a schematic diagram showing a menu management interface of a medical system according to an embodiment of the present disclosure.
[0035] It should be understood that the size of each part shown in the accompanying drawings is not drawn according to the actual proportional relationship. In addition, the same or similar reference numerals represent the same or similar components. DETAILED DESCRIPTION
[0036] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The description of the exemplary embodiments is merely illustrative and is in no way intended to limit the present disclosure and its application or use. The present disclosure can be implemented in many different forms and is not limited to the embodiments described herein. These embodiments are provided to make the present disclosure thorough and complete and to fully express the scope of the present disclosure to those skilled in the art. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the composition of the materials, the numerical expressions and the numerical values set forth in these embodiments should be interpreted as being merely exemplary and not as limiting.
[0037] The words "first", "second" and similar words used in this disclosure do not indicate any order, quantity or importance, but are only used to distinguish different parts. The words "include" or "comprise" and similar words mean that the elements before the word include the elements listed after the word, and do not exclude the possibility of also including other elements.
[0038] All terms (including technical terms or scientific terms) used in the present disclosure have the same meanings as those understood by ordinary technicians in the field to which the present disclosure belongs, unless otherwise specifically defined. It should also be understood that terms defined in general dictionaries, such as general dictionaries, should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an idealized or extremely formal sense, unless explicitly defined herein.
[0039] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.
[0040] The inventor of the present disclosure found that in the relevant technology, the medical system has weak support for group management. For large and medium-sized medical institutions, basically each medical institution is managed as a separate individual. Although some medical systems provide organizational structure and authority management functions, there are too many restrictions and the functions cannot be issued, resulting in more operation and maintenance work for each system online. Over time, the operation and maintenance work of the system itself is very cumbersome.
[0041] In view of this, an embodiment of the present disclosure provides a method for managing permissions in a medical system, which can minimize the burden of operation and maintenance.
[0042] Figure 1 FIG. 1 is a flowchart showing a method for managing the rights of a medical system according to an embodiment of the present disclosure. Figure 1 As shown, the permission management method includes steps S102 to S104.
[0043] In step S102, in response to the role setting operation of the first-level administrator corresponding to the medical group layer, a second-level administrator is established for the hospital, and the corresponding menu, function and data access rights are assigned to the second-level administrator. The hospital is a subordinate institution of the medical group layer. Here, the functions corresponding to the second-level administrator are the functions that the second-level administrator can implement through the medical system (for example, they may include: logging into the system, viewing information, department settings and role settings, etc.); the menu can visualize these functions for the second-level administrator to select and click.
[0044] For example, initially the system will establish an account for a first-level administrator (or super administrator) in the database so that the first-level administrator can log in and configure the menu permissions corresponding to this account. The first-level administrator is the administrator at the group level. The medical group can include different hospitals, that is, the hospital is a subordinate organization at the group level. The first-level administrator logs in to the medical system by entering the account, password and verification code. The medical system can return the corresponding menu permissions based on the permissions of the current account. The first-level administrator can establish role identifications for first-level administrators and second-level administrators through the medical system. For example, the administrator of each hospital can act as a second-level administrator, and the second-level administrator can choose the corresponding hospital.
[0045] It should be noted that the role ID is a mark used to identify a role. The role ID includes: the role ID of the first-level administrator, the role ID of the second-level administrator, and the role ID of the user. After a role is selected, the role ID can be set for the role. Each role ID is set with a corresponding menu permission.
[0046] After the first-level administrator performs the role setting operation, the medical system responds to the role setting operation, creates a second-level administrator for the corresponding hospital, and assigns the corresponding menu, function, and data access permissions to the second-level administrator. For example, the medical system can issue the menu, function, and data access permissions corresponding to the second-level administrator to the subsystem corresponding to the hospital. Since specific function menus are selected, the second-level administrator can see these function menus after logging into the system, and can see the specific function page after clicking.
[0047] In step S104, in response to the role setting operation of the second-level administrator, the menu, function and data access rights corresponding to the user are allocated to the user. Here, the functions corresponding to the user are the functions that the user can implement through the medical system (for example, they may include: logging into the system and viewing information, etc.); the menu can visualize these functions for the user to select and click.
[0048] For example, after the second-level administrator (or hospital administrator) logs into the system by entering the account, password and verification code, the medical system can return the corresponding menu permissions according to the permissions of the current account. The second-level administrator can establish role identifications for second-level administrators and users (such as employees, customers or patients) through the medical system. Roles can include multiple roles, such as follow-up doctors, chronic disease doctors, nurses or marketing personnel, etc. The second-level administrator can select the corresponding hospital and configure permissions (i.e., select function menus). When a specific function menu is selected, the second-level administrator can see these function menus after logging into the system, and click on these function menus to see the specific function pages. After the second-level administrator performs the role setting operation, the medical system responds to the role setting operation and assigns the user the menu, function and data access permissions corresponding to the user.
[0049] So far, a permission management method for a medical system according to some embodiments of the present disclosure is provided. The method includes: in response to the role setting operation of the first-level administrator corresponding to the medical group layer, establishing a second-level administrator for the hospital, and assigning corresponding menu, function and data access rights to the second-level administrator; and in response to the role setting operation of the second-level administrator, assigning the menu, function and data access rights corresponding to the user to the user. In this method, the medical system adopts a method of allocating corresponding menu, function and data access rights to the next-level administrator or user in response to the role setting operation of the previous-level administrator, thereby facilitating operation and maintenance management and minimizing the operation and maintenance burden.
[0050] In some embodiments, the hospital may include: a first hospital and a second hospital different from the first hospital. The second-level administrator may include: a first administrator and a second administrator different from the first administrator. For example, the menu, function, and data access rights corresponding to the first administrator are different from the menu, function, and data access rights corresponding to the second administrator. In this embodiment, different second-level administrators may be established for different hospitals, and different menu, function, and data access rights may be assigned to different second-level administrators. In this way, diversified settings for second-level administrators can be achieved, thereby improving the management level.
[0051] In some embodiments, the users may include: a first user and a second user different from the first user. For example, the menu, function, and data access rights corresponding to the first user are different from the menu, function, and data access rights corresponding to the second user. In this embodiment, different menu, function, and data access rights may be assigned to different users. This can achieve diversified settings for users and improve management level.
[0052] In some embodiments, the permission management method may further include: adding, deleting or modifying organizational structure information in the medical system in response to the organizational maintenance operation of the first-level administrator. For example, the organizational structure information may be added, deleted or modified in the medical system before the second-level administrator is established for the hospital. For example, the organizational structure information may be in the form of a tree menu. The organizational structure information may include a region and a hospital. The region includes a subclass, and the subclass includes a hospital or a region of the next level, and the hospital is the last node of the organizational structure information.
[0053] For example, Fig. 9 is a schematic diagram showing an organization management interface of a medical system according to an embodiment of the present disclosure. Fig. 9 As shown in the figure, the region can be: North China, East China, etc. Fig. 9 In the above example, the parent organization refers to the parent organization of the current organization (i.e., the parent node). For example, if the current organization is North China, then the parent organization is XXX Company. The organization name refers to the name of the current organization, such as North China. In addition, Fig. 9 The business unit is shown in FIG. 1 , which may be an organization at the same level as the region, for example, Fig. 9 In other embodiments, the business unit may be a lower-level organization in the region and a higher-level organization in the hospital.
[0054] like Fig. 9 As shown in the figure, when you click "Add", you can Fig. 9 Fill in the information of the currently added institution on the right side of the , and you can fill in the superior institution, institution name, contact number and remarks of the current institution. Filling in the superior institution can make it clear which institution is the superior institution of the current institution, filling in the institution name can make it clear what institution the current institution is, filling in the contact number can facilitate personnel to contact the institution by phone, and the remarks information can be any information that needs to be noted. The contact number and remarks information here can also be left blank. The interface for selecting "hospital" here is similar to the interface for selecting "region / division", which also includes the superior institution, institution name, contact number and remarks, etc. In the above embodiment, the first-level administrator can set the organizational structure of the entire medical system through the medical system. The organizational structure can be in the form of a tree menu. The organizational structure is divided into two categories: region (or division) and hospital. The hospital is a leaf node, that is, the bottom layer of nodes, so the hospital has no subclasses, and only the region (or division) can establish the next level of nodes. This realizes the first administrator's setting of the organizational structure of the medical system.
[0055] In some embodiments of the present disclosure, the parent organization of any node in the organizational structure can be modified. If there are subclasses under the node, the subclasses can also be modified. Fig. 9As shown in the figure, move the mouse to an organization, for example, to the "North China Region", click on the organization, and then click "Edit", you can modify the information of the "North China Region" (i.e. the superior organization, organization name, contact number and remarks information).
[0056] Fig. 9 "Delete" is used to delete an institution. For example, move the mouse to an institution, click it, and then click "Delete" to delete it. If the deleted node contains subclasses, all its subclasses will be deleted together. For example, if you delete "North China Region", "XX Hospital" under "North China Region" will also be deleted.
[0057] In some embodiments, the permission management method may further include: adding, deleting or modifying department information in the hospital architecture in response to the department maintenance operation of the second-level administrator. For example, department information may be added, deleted or modified in the hospital architecture before the corresponding menu, function and data access rights are assigned to the user. For example, the departments here may be different departments, etc.
[0058] For example, Fig.10 FIG. 1 is a schematic diagram showing a department management interface of a medical system according to an embodiment of the present disclosure. Fig.10 As shown, departments may include: geriatric outpatient clinic, urology, urology outpatient clinic, internal medicine outpatient clinic, and surgical outpatient clinic. The superior department refers to the department above the current department. The department name refers to the name of the current department. For example, if the current department is the urology outpatient clinic, the superior department of the current department is the urology department.
[0059] like Fig.10 As shown in the figure, when you click "Add", you can Fig.10 Fill in the information of the currently added department on the right side. You can fill in the parent department, department name and department description of the current department. Filling in the parent department can clarify which department is the parent department of the current department, filling in the department name can clarify what department the current department is, and the department description can be any information needed to describe the department (such as the contact information of the department, etc.).
[0060] When you need to modify the information of a department, such as Fig.10 As shown, you can move the mouse to a department, for example, to "Urology Clinic", click "Urology Clinic", and then click "Edit" to modify the information of the "Urology Clinic" (i.e., the superior department, department name and department description).
[0061] Fig.10"Delete" is used to delete a department. For example, move the mouse to a department (such as "Urology"), click the department, and then click "Delete" to delete the department (such as "Urology"). If the deleted department contains subcategories, all its subcategories will be deleted together. For example, if you delete "Urology", the "Urology Clinic" under "Urology" will also be deleted.
[0062] In the above embodiment, the second-level administrator sets the hospital's department structure through the medical system. For example, the department structure can be in the form of a tree menu. The department structure can be set up in multiple levels, and the parent department of any node can be modified. If the node has subclasses, the subclasses can also be modified. If the node is deleted, all its subclasses will be deleted. This enables the second-level administrator to set up hospital departments.
[0063] In some embodiments, the permission management method may further include: in response to the information configuration operation of the first-level administrator, configuring the administrator information of the second-level administrator. In the above embodiment, the first-level administrator can establish administrator information of different second-level administrators through the medical system (for example, it may include account number, password, identity information (such as ID number) and mini-program permissions, etc.). For example, the first-level administrator can add a second-level administrator's account number, password, identity information (such as ID number) and mini-program permissions, etc. in the user management interface. For example, Fig.12 As shown in the figure, after clicking "Add", an add window will pop up, in which the above information can be added. This implements the configuration of the administrator information of the second-level administrator. Each second-level administrator can log in to the system according to the established account and password. After logging in, the second-level administrator can see the menus, functions and data access permissions corresponding to this account.
[0064] Here, the medical system can be loaded on the mobile communication terminal in the form of a mini program. Both the administrator and the user have mini program permissions, that is, both the administrator and the user can use the mini program to log in and use the medical system. This makes it more convenient to use and improves the convenience of the medical system.
[0065] In some embodiments, when the medical system is used for the first time, a first-level administrator may be predefined in the medical system. For example, the information of the first-level administrator may be written into the medical system.
[0066] For example, Fig.11is a schematic diagram showing a role management interface of a medical system according to an embodiment of the present disclosure. Here, the role management interface contains some role information, while the second-level administrator's account, password, identity information, and applet permissions belong to the administrator's user information, which are different. Specifically, Fig.11 As shown in the figure, the role information may include: serial number, role name, role ID, role description, affiliated hospital, creation time and operation. The serial number is the serial number of a role. The role name is the name of a role. The role ID refers to the role ID corresponding to a role. For example, the role ID of the role name doctor is the first-level administrator (i.e. Fig.11 The role name is XX Hospital Administrator, and the role ID is the second-level administrator (i.e. Fig.11 Hospital Administrator in ). Role description is a simple description of the role. For example, if the role ID of a role is a first-level administrator, the role description of the role can be a first-level administrator. The role description here can be any description of the role, which can facilitate personnel to understand some attributes of the role, etc. The affiliated hospital refers to the hospital to which the current role belongs. The creation time refers to the time when the role was created. Operations include: edit, delete, and permissions. Here, "Edit" is used to modify the relevant content of a role (for example, it can include information such as serial number, role description, role ID, role description and affiliated hospital), "Delete" is used to delete a role, and "Permissions" are used to set the permissions of a role. For example, when you click "Permissions", you can see all the permissions corresponding to the role ID to which the role belongs, and then you can set the corresponding permissions for the role by checking the boxes.
[0067] For example, the permissions of the first-level administrator (i.e., the menus that the first-level administrator can manage) include: system management, patient center, follow-up center, AI (Artificial Intelligence) intelligence and data statistics; the permissions of the second-level administrator (i.e., the menus that the second-level administrator can manage) include: patient center, follow-up center, AI intelligence and data statistics; the permissions of the user (i.e., the menus that the user can manage) include: patient center, follow-up center and AI intelligence.
[0068] In some embodiments, the permission management method may further include: configuring user information of the user in response to an information configuration operation of the second-level administrator.
[0069] In the above embodiment, the second-level administrator can establish user information of different users through the medical system (for example, it can include account number, password, identity information and mini-program permissions, etc.). This enables the configuration of user information of the user. For example, the second-level administrator can add a user's account number, password, identity information (such as ID number) and mini-program permissions, etc. in the user management interface. For example, Fig.12 As shown in the figure, when you click "Add", the add window will pop up and you can add the above information in the add window. Each user can log in to the system according to the established account and password. After the user logs in, the system can assign corresponding menu, function and data access permissions according to the permissions of this account.
[0070] For example, Fig.12 is a schematic diagram showing a user management interface of a medical system according to an embodiment of the present disclosure. Fig.12 As shown, the user's information may include: serial number, user name, name, mobile phone number, gender, affiliated hospital, affiliated department, role, status and operation. The serial number is the serial number of a certain user. The user name is the name of a certain user. The mobile phone number is the mobile phone number of a certain user. The affiliated hospital is the hospital to which a certain user belongs. For example, the hospital to which the user with the serial number "00000030" belongs is XX Hospital. The affiliated department is the department to which a certain user belongs. For example, the department to which the user with the serial number "00000030" belongs is the Department of Gastroenterology. The role is the role of a certain user. For example, the role of the user with the serial number "00000030" is the administrator of XX Hospital. The status indicates whether the status of a certain user is valid. "Valid" means that the corresponding user can log in to the system, and "locked" means that the corresponding user cannot log in to the system. Operations may include editing and deleting. "Edit" is used to modify the operation of the relevant content of a certain user. For example, by clicking "Edit" behind a certain user, you can modify the serial number, user name, name, mobile phone number, gender, affiliated hospital, affiliated department, role and status of the user. "Delete" is used to delete the operation of a certain user.
[0071] In some embodiments, the permission management method may further include: in response to a menu setting operation of a first-level administrator, configuring a plurality of menu functions. Each menu function corresponds to a role identifier of at least one of a first-level administrator, a second-level administrator, and a user. For example, before a second-level administrator is established for a hospital and after organizational structure information is added, deleted, or modified in a medical system, in response to a menu setting operation of a first-level administrator, configuring a plurality of menu functions.
[0072] For example, Fig.13 is a schematic diagram showing a menu management interface of a medical system according to an embodiment of the present disclosure. Fig.13As shown, the menu may include: system management, patient center, follow-up center, AI intelligence and data statistics, etc. You can add, edit or delete a menu as needed. For example, select the "System Management" menu with the mouse, and then click "Add" to add a next-level menu to the "System Management" menu. When adding a next-level menu, you can set the parent node, title and permission identifier of the next-level menu. Here, the parent node refers to the previous level menu of the next-level menu, the title refers to the name of the next-level menu, and the permission identifier refers to which one or several of the first-level administrator, second-level administrator and user have the permission for the next-level menu. For example, in the process of setting a menu function, when you click the add box of the permission identifier, three role identifiers of the first-level administrator, second-level administrator and user will pop up, and you can select which one or several of the first-level administrator, second-level administrator and user have the permission for the menu by checking.
[0073] In addition, if Fig.13 As shown, when adding a next-level menu, you can also set the icon, resource path, request method, type, sort, front-end component and front-end address of the next-level menu. Here, the resource path can be the URL (Uniform Resource Location) of a menu function. The request method can be selected as the post method or the get method. The type is the resource request type. The sort is the serial number of the added menu, for example, the serial number can be entered manually. The description content of the menu can be entered in the box behind "Front-end Component", for example, it can be any description content. The front-end address is the address of the added menu. The menu page corresponding to the address can be directly reached through the front-end address.
[0074] When you need to modify a menu function, you can select it with the mouse and click "Edit" to modify it. When you need to delete a menu function, you can select it with the mouse and click "Delete" to delete it.
[0075] In the above embodiment, the first-level administrator can set all the function menus of the entire medical system through the medical system. Each function menu corresponds to its role identification (that is, which role identifications have the authority to see this function menu and have the authority to select this menu). Menu management can be dynamically configured. Through configuration operations, the medical system can directly correspond to the front-end page, and then when selecting the role's authority, the corresponding function page can be displayed according to the selected menu. Therefore, the medical system has relatively good flexibility and scalability.
[0076] Figure 2FIG. 1 is a flowchart showing a method for managing the rights of a first-level administrator in a medical system according to an embodiment of the present disclosure. Figure 2 As shown, the method may include steps S202 to S208.
[0077] In step S202, in response to the organization maintenance operation of the first-level administrator, the organization structure information is added, deleted or modified in the medical system.
[0078] Here, the organizational structure can be maintained by the first-level administrator, using a tree-shaped hierarchical structure, and the number of layers can be unlimited. In the organizational structure, the hospital level can have an identifier, which can identify the level as a hospital.
[0079] In some embodiments, the authority management method may further include: in the process of modifying the organizational structure information, modifying the parent organization corresponding to the currently adjusted organization and ensuring that the address identifier of the currently adjusted organization remains unchanged. The historical medical data of the currently adjusted organization is stored in the address identifier.
[0080] In this embodiment, when the organizational structure is adjusted, the parent organization (i.e., the upper-level organization) corresponding to the currently adjusted organization can be modified, and the address identifier (ID) of the currently adjusted organization can be ensured to remain unchanged, thereby not affecting the historical medical data stored in the address identifier.
[0081] In some embodiments, the organizational structure can be a one-layer structure of a single hospital, a two-layer structure of a medical group and a hospital, or a four-layer structure of a medical group, a region, a business unit, and a hospital. For example, the medical group is the upper level organization of the region, the region is the upper level organization of the business unit, and the business unit is the upper level organization of the hospital. In other embodiments, the region and the business unit can be the same level organization.
[0082] In step S204, in response to the menu setting operation of the first-level administrator, a plurality of menu functions are configured.
[0083] For example, when a new menu is added, in response to a menu setting operation by a first-level administrator, the medical system may select a role identifier corresponding to the newly added menu.
[0084] In step S206, in response to the role setting operation of the first-level administrator, a second-level administrator is established for the hospital, and corresponding menu, function and data access rights are allocated to the second-level administrator.
[0085] For example, in response to the role setting operation of the first-level administrator, the medical system can create a role, and the role can have a role identifier (including the first-level administrator, the second-level administrator, and the user). After creating the role, the first-level administrator can also authorize the role. When authorizing the role, the medical system can display the corresponding menu according to the role identifier, and then the first-level administrator can select a specific menu from it and complete the role authorization after saving.
[0086] In step S208, in response to the information configuration operation of the first-level administrator, the administrator information of the second-level administrator is configured.
[0087] For example, in response to the information configuration operation of the first-level administrator, the medical system can configure the hospital to which the second-level administrator belongs and the corresponding second-level administrator role, and then set the login name and password. The medical system can also generate an administrator list, which includes the administrator information of the second-level administrators of each hospital.
[0088] So far, a permission management method for first-level administrators of a medical system according to some embodiments of the present disclosure is provided. In this method, after the first-level administrator logs into the system, the medical system responds to the organization maintenance operation of the first-level administrator to add, delete or modify the organizational structure information in the medical system; then, the medical system responds to the menu setting operation of the first-level administrator to configure the menu function, and each menu function can correspond to at least one role identifier; then, the medical system responds to the role setting operation of the first-level administrator to assign a second-level administrator to the hospital, and assigns the corresponding menu, function and data access rights to the second-level administrator; next, the medical system responds to the information configuration operation of the first-level administrator to configure the administrator information of the second-level administrator. In this way, the corresponding setting of the medical system in response to the relevant operations of the first-level administrator is realized, which can facilitate the maintenance and management of the group.
[0089] In the above embodiment, the role management step (S206) can be performed after the organization management step (S202) and the menu management step (S204), and the user management step (S208) can be performed after the role management step. In other words, the role management step can depend on the organization management step and the menu management step, and the user management step can depend on the role management step.
[0090] Figure 3 FIG. 1 is a flow chart showing a method for managing the rights of a second-level administrator in a medical system according to an embodiment of the present disclosure. Figure 3 As shown, the method may include steps S302 to S306.
[0091] In step S302, in response to the department maintenance operation of the second-level administrator, department information is added, deleted or modified in the hospital structure. That is, after the second-level administrator logs into the system, he can maintain the department structure of the corresponding hospital.
[0092] In step S304, in response to the role setting operation of the second-level administrator, menu, function and data access rights corresponding to the user are allocated to the user.
[0093] For example, in response to the role setting operation of the second-level administrator, the medical system can maintain the roles of the hospital (e.g., doctors, nurses, and administrators, etc.), and authorize the roles after creating them. When authorizing roles, the medical system can display the corresponding menu according to the role identifier, and then the second-level administrator can select a specific menu from it and complete the role authorization after saving.
[0094] In some embodiments, the second-level administrator cannot select the role identification of the first-level administrator when creating a role, nor can he see the menu corresponding to the role identification of the first-level administrator, nor can he operate the functions of the first-level administrator.
[0095] In step S306, in response to the information configuration operation of the second-level administrator, user information of the user is configured.
[0096] In response to the information configuration operation of the second-level administrator, the medical system can maintain the users of the hospital where the second-level administrator is located. For example, the second-level administrator can select the department to which the user belongs and the corresponding role, and then set the login name and password. The medical system can generate a user list, which includes the user information of the hospital.
[0097] So far, a permission management method for a second-level administrator of a medical system according to an embodiment of the present disclosure is provided. In this method, after the second-level administrator logs in to the system, the medical system responds to the department maintenance operation of the second-level administrator to add, delete or modify department information in the hospital's architecture; then, the medical system responds to the role setting operation of the second-level administrator to assign menu, function and data access rights corresponding to the user to the user; next, the medical system responds to the information configuration operation of the second-level administrator to configure the user information of the user. In this way, the corresponding setting of the medical system in response to the relevant operations of the second-level administrator is realized, which can facilitate the maintenance management of the group.
[0098] In the above embodiment, the user management step (S306) may be performed after the department management step (S302) and the role management step (S304). In other words, the user management step may be dependent on the department management step and the role management step.
[0099] In some embodiments, the first-level administrator is responsible for the organizational settings, menu settings, and specific role settings and user settings of the entire system, and can set up the second-level administrator for each hospital. The first-level administrator can create first-level administrators and second-level administrators through the medical system. The second-level administrator is responsible for the department settings, role settings, and user settings of each hospital. The second-level administrator can establish hospital administrators and users (such as employees) through the medical system. The user can be a different role. Different roles have different business system menus, functions, and data access permissions. Users with different roles can have different system menus, functions, and data access permissions after entering the system. In some embodiments, employees of each hospital can only see the relevant functions and data of their own hospital.
[0100] Combine the following Figure 4 Describe in detail the management process for these administrators and users.
[0101] Figure 4 FIG. 1 is a flowchart showing a method for managing the rights of a medical system according to another embodiment of the present disclosure. Figure 4 As shown, the method may include steps S402 to S416.
[0102] In step S402, the first-level administrator first enters the organization management interface to set the organizational structure of the entire medical system.
[0103] In step S404, the first-level administrator establishes the role of the second-level administrator and allocates corresponding menu, function and data access rights to the second-level administrator.
[0104] In step S406, the first-level administrator establishes different administrator information for the second-level administrator, such as account number, password, ID card, and mini-program permissions.
[0105] In step S408, the second-level administrator enters the account number, password and verification code to log into the system.
[0106] In step S410, the second-level administrator enters the department management interface to maintain the department structure of the hospital for which he is responsible.
[0107] In step S412, the second-level administrator enters the role management interface and establishes the user's role identification.
[0108] In step S414, the second-level administrator performs user maintenance, selects roles and departments for users, and establishes user information for different users, such as account numbers, passwords, ID cards, and mini-program permissions.
[0109] In step S416, the user logs into the system and can view the system menus, functions, data access permissions assigned to him / her, as well as functions and data related to his / her hospital.
[0110] For example, when the user is a doctor, the doctor's professional title level (such as chief physician, deputy chief physician or attending physician, etc.) and the doctor's professional expertise can be selected and maintained. The medical system can provide doctors with options for service types (for example, graphic consultation, interpretation of physical examination reports, and video consultation, etc.). For another example, when a patient, as a user, selects a service through a mobile communication terminal, he can obtain a corresponding list of doctors and view the professional title and professional expertise information of each doctor. Therefore, the medical system can obtain the service applied for by the user according to the type of service provided to the user, and make corresponding replies or interpretations. For example, a doctor can have PC-side permissions and mini-program permissions, that is, the doctor can perform corresponding processing through the PC-side program or the mobile communication terminal mini-program; the patient has mini-program permissions but no PC-side permissions, that is, the patient can only perform corresponding processing through the mobile communication terminal mini-program.
[0111] Thus, another embodiment of the present disclosure provides a method for managing the rights of a medical system. Through the method, the matters that the first-level administrator, the second-level administrator, and the user are responsible for and the related operations that can be performed can be known. Such a system setting facilitates the maintenance of the medical system.
[0112] In the above-mentioned permission management method for the medical system, the first-level administrator at the group level is responsible for maintaining the organizational structure, creating a second-level administrator for the hospital, and granting the second-level administrator the authority to manage the hospital. After the second-level administrator logs into the system, he manages the departments, roles, users, and permissions of his own hospital. After logging into the system, the user can use the system functions normally. In this way, this method not only meets the requirements of group management, but also enables the hospital to be managed as a separate individual, hierarchical and graded management permissions, and evenly distribute the work of each administrator, thereby reducing the system operation and maintenance work. Moreover, the above-mentioned method also provides users with operational functions.
[0113] In some embodiments, the organization management step may be performed first, then the department management step, then the menu management step, then the role management step, and then the user management step. In other words, the department management step may depend on the organization management step, the role management step may depend on the organization management step and the menu management step, and the user management step may depend on the department management step and the role management step.
[0114] In some embodiments, when a hospital does not have a corresponding second-level administrator, the first-level administrator may be granted management authority for the corresponding hospital to perform hospital-level data maintenance. After maintaining the hospital's department and user data, the group-level organizational structure may automatically obtain the hospital's department and user numbers.
[0115] Figure 5FIG. 1 is a schematic diagram showing the structure of a medical system according to an embodiment of the present disclosure. Figure 5 As shown, the medical system may include a receiving module 502 and a role management module 504 .
[0116] The receiving module 502 is used to receive a role setting operation of a first-level administrator corresponding to the medical group layer or a role setting operation of a second-level administrator corresponding to the hospital. The hospital is a subordinate institution of the medical group layer.
[0117] The role management module 504 is used to respond to the role setting operation of the first-level administrator, establish a second-level administrator for the hospital, and assign corresponding menu, function and data access permissions to the second-level administrator, and respond to the role setting operation of the second-level administrator to assign menu, function and data access permissions corresponding to the user to the user. Here, the role management module 504 can be used to design the role of each hospital and configure the menu, function and data access permissions corresponding to the role.
[0118] So far, a medical system according to some embodiments of the present disclosure is provided. The medical system includes a receiving module and a role management module. The receiving module is used to receive a role setting operation of a first-level administrator corresponding to the medical group layer or a role setting operation of a second-level administrator corresponding to the hospital. The role management module is used to assign a second-level administrator to the hospital in response to the role setting operation of the first-level administrator, and assign corresponding menu, function and data access rights to the second-level administrator, and assign menu, function and data access rights corresponding to the user to the user in response to the role setting operation of the second-level administrator. The medical system can facilitate the operation and maintenance management of the system and minimize the operation and maintenance burden of the system.
[0119] Figure 6 FIG. 2 is a schematic diagram showing the structure of a medical system according to another embodiment of the present disclosure. Figure 6 As shown, the medical system may include a receiving module 502 and a role management module 504 .
[0120] In some embodiments, Figure 6 As shown, the medical system may also include an organization management module 606. The organization management module 606 is used to add, delete or modify organizational structure information in the medical system in response to the organization maintenance operation of the first-level administrator. Therefore, the organization management module 606 can be used to define, design and maintain an organization hospital.
[0121] In some embodiments, Figure 6As shown, the medical system may also include a department management module 608. The department management module 608 is used to add, delete or modify department information in the hospital architecture in response to the department maintenance operation of the second-level administrator. Therefore, the department management module 608 can be used for the definition, design and maintenance of each department in each hospital.
[0122] In some embodiments, Figure 6 As shown, the medical system may further include a user management module 610. The user management module 610 is used to configure the administrator information of the second-level administrator in response to the information configuration operation of the first-level administrator, and to configure the user information of the user in response to the information configuration operation of the second-level administrator. For example, the user management module 610 can be used to create users, identity information, role information (the role has been assigned PC (Personal Computer) end permissions) and mobile end permission information for each hospital, and can set valid or locked status for the user.
[0123] In some embodiments, Figure 6 As shown, the medical system may further include a menu management module 612. The menu management module 612 is used to configure multiple menu functions in response to the menu setting operation of the first-level administrator. Each menu function corresponds to a role identifier of at least one of the first-level administrator, the second-level administrator, and the user. Here, the menu management module 612 can be used for the configuration, design, maintenance of each menu function in the system, and the configuration of the corresponding relationship with the front-end page.
[0124] In some embodiments, relevant data of the role management module 504, the organization management module 606, the department management module 608, the user management module 610 and the menu management module 612 may be stored in a database.
[0125] In some embodiments, the medical system may include at least one of a PC-side system and a mobile communication side (or mini-program side) system. For example, the system on the PC side can be used by hospital staff, and the mini-program side on the mobile communication side can be used by hospital staff and customers. Of course, those skilled in the art will understand that the medical system can be set only on the PC side, or can also be set only on the mobile communication side, or can also be set on both the PC side and the mobile communication side.
[0126] Users on the PC side can have three role identifications: first-level administrator, second-level administrator, and hospital employee (a type of user). It should be noted that the role identification here is not equal to the role. The role identification can distinguish the functional modules that can be seen for selection. The roles on the PC side can be set by the first-level administrator and the second-level administrator. There is no limit on the number and they can be configured according to the specific needs of each hospital. The first-level administrator can establish first-level administrators and second-level administrators, and the second-level administrator can establish administrators and users of his own hospital. For example, a user can be an employee, and an employee can have various different roles. The first-level administrator is responsible for the organization management module, menu management module, role management module, and user management module. The second-level administrator is responsible for the department management module, role management module, and user management module.
[0127] The mini program can be applied to four types of roles: administrator, doctor / nurse, visitor / customer, and marketing staff. Here, employees, doctors / nurses, visitors / customers, and marketing staff are all users of specific functions. Employees can see the function pages corresponding to specific menus (for example, chronic disease card, follow-up management, health prescriptions, graphic consultation, gadgets, and statistics).
[0128] In the above medical system, each second-level administrator can set various roles for his own hospital and assign different permissions to the roles to meet the needs of different hospitals that may have different roles and different permissions. The data of each hospital does not interfere with each other. Each user can have multiple roles, and there is no need to set separate permissions for the user. Different role permissions can be assigned according to the role characteristics set by the user to achieve the final user permission setting. The role permissions of users on the PC and mobile communication terminals (such as mobile phones) are separate and can be adjusted according to needs, thereby increasing the flexibility and scalability of the system. The administrator of each hospital can set the department level of his own hospital. Departments and various functional data between hospitals do not affect each other, making the system settings more flexible.
[0129] The above medical system can fully meet the expansion and change adjustment of the multi-level organizational structure without any restrictions and without affecting historical medical data. In this medical system, permissions are managed hierarchically and corresponding functions are issued, so that management work can be evenly distributed and the difficulty of operation and maintenance can be reduced. In addition, each piece of medical data can be made to correspond to the organizational code, so that the group level can achieve unified acquisition of the operation data of each institution.
[0130] Figure 7 7 is a schematic diagram showing the structure of a medical system according to another embodiment of the present disclosure. The medical system includes a memory 710 and a processor 720. Among them:
[0131] The memory 710 can be a disk, a flash memory, or any other non-volatile storage medium. The memory is used to store Figures 1 to 4 At least one of the corresponding embodiments of the instructions.
[0132] The processor 720 is coupled to the memory 710 and can be implemented as one or more integrated circuits, such as a microprocessor or a microcontroller. The processor 720 is used to execute instructions stored in the memory, which can facilitate the operation and maintenance management of the system and minimize the operation and maintenance burden of the system.
[0133] In some embodiments, it is also possible to Figure 8 As shown, the medical system 800 includes a memory 810 and a processor 820. The processor 820 is coupled to the memory 810 via a BUS bus 830. The medical system 800 can also be connected to an external storage device 850 via a storage interface 840 to call external data, and can also be connected to a network or another computer system (not shown) via a network interface 860, which will not be described in detail here.
[0134] In this embodiment, the data instructions are stored in the memory and then processed by the processor, which can facilitate the operation and maintenance management of the system and minimize the operation and maintenance burden of the system.
[0135] In some other embodiments, the present invention further provides a non-transitory computer-readable storage medium having computer program instructions stored thereon, which when executed by a processor implements Figures 1 to 4 The present invention may be implemented as a method, an apparatus, or a computer program product. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0136] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1A device that provides the functions specified in a block or multiple blocks.
[0137] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0138] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0139] So far, various embodiments of the present disclosure have been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.
[0140] Although some specific embodiments of the present disclosure have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified or some technical features may be replaced by equivalents without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims
1. A method for managing rights in a medical system, comprising: In response to a role setting operation of a first-level administrator corresponding to the medical group layer, a second-level administrator is established for a hospital, and corresponding menu, function and data access rights are assigned to the second-level administrator, wherein the hospital is a subordinate institution of the medical group layer; In response to the role setting operation of the second-level administrator, assigning to the user menu, function and data access rights corresponding to the user; and In response to the organization maintenance operation of the first-level administrator, adding, deleting or modifying the organization structure information in the medical system; Wherein, in the process of modifying the organizational structure information, the parent organization corresponding to the currently adjusted organization is modified, and the address identifier of the currently adjusted organization is ensured to remain unchanged, wherein the historical medical data of the currently adjusted organization is stored in the address identifier; The rights management method further includes: In response to the menu setting operation of the first-level administrator, a plurality of menu functions are configured, wherein each menu function corresponds to a role identifier of at least one of the first-level administrator, the second-level administrator and the user, and when a new menu is added, in response to the menu setting operation of the first-level administrator, the medical system selects a role identifier corresponding to the new menu; Among them, the first-level administrator sets all functional menus of the entire medical system through the medical system, wherein the menu management is dynamically configured. Through the configuration operation, the medical system directly corresponds to the front-end page. When selecting the role's authority, the corresponding functional page is displayed according to the selected menu.
2. The rights management method according to claim 1, wherein: The hospitals include: a first hospital and a second hospital different from the first hospital, The second-level administrator includes: a first administrator and a second administrator different from the first administrator, The menu, function, and data access rights corresponding to the first administrator are different from the menu, function, and data access rights corresponding to the second administrator.
3. The rights management method according to claim 1, wherein: The users include: a first user and a second user different from the first user, The menu, function and data access rights corresponding to the first user are different from the menu, function and data access rights corresponding to the second user.
4. The rights management method according to any one of claims 1 to 3, further comprising: In response to the department maintenance operation of the second-level administrator, department information is added, deleted or modified in the hospital's architecture.
5. The rights management method according to any one of claims 1 to 3, further comprising: In response to the information configuration operation of the first-level administrator, configuring administrator information of the second-level administrator; as well as In response to the information configuration operation of the second-level administrator, user information of the user is configured.
6. The rights management method according to claim 1, wherein: The organizational structure information adopts a tree menu format, and the organizational structure information includes regions and hospitals; The region includes subcategories, and the subcategories include the hospital or a region at a lower level, and the hospital is the last node of the organizational structure information.
7. A medical system comprising: A receiving module, used to receive a role setting operation of a first-level administrator corresponding to a medical group layer or a role setting operation of a second-level administrator corresponding to a hospital, wherein the hospital is a subordinate institution of the medical group layer; a role management module, configured to establish a second-level administrator for the hospital in response to the role setting operation of the first-level administrator, and assign corresponding menu, function and data access permissions to the second-level administrator, and to assign menu, function and data access permissions corresponding to the user to the user in response to the role setting operation of the second-level administrator; and an organization management module, configured to add, delete or modify organization structure information in the medical system in response to the organization maintenance operation of the first-level administrator; Wherein, in the process of modifying the organizational structure information, the parent organization corresponding to the currently adjusted organization is modified, and the address identifier of the currently adjusted organization is ensured to remain unchanged, wherein the historical medical data of the currently adjusted organization is stored in the address identifier; The medical system further comprises: a menu management module, configured to configure a plurality of menu functions in response to the menu setting operation of the first-level administrator, wherein each menu function corresponds to a role identifier of at least one of the first-level administrator, the second-level administrator and the user, and when a new menu is added, in response to the menu setting operation of the first-level administrator, the medical system selects the role identifier corresponding to the new menu; Among them, the first-level administrator sets all functional menus of the entire medical system through the medical system, wherein the menu management is dynamically configured. Through the configuration operation, the medical system directly corresponds to the front-end page. When selecting the role's authority, the corresponding functional page is displayed according to the selected menu.
8. The medical system according to claim 7, further comprising: The department management module is used to add, delete or modify department information in the hospital architecture in response to the department maintenance operation of the second-level administrator.
9. The medical system according to claim 7, further comprising: The user management module is used to configure the administrator information of the second-level administrator in response to the information configuration operation of the first-level administrator, and to configure the user information of the user in response to the information configuration operation of the second-level administrator.
10. A medical system comprising: Memory; as well as A processor coupled to the memory, wherein the processor is configured to execute the method according to any one of claims 1 to 6 based on instructions stored in the memory.
11. A non-transitory computer-readable storage medium having computer program instructions stored thereon, which, when executed by a processor, implement the method according to any one of claims 1 to 6.
Citation Information
Patent Citations
Remote medical comprehensive service platform based on mobile Internet
CN106952205A
