CN110633278A - Method for generating patient hospitalization registration form - Google Patents
Method for generating patient hospitalization registration form Download PDFInfo
- Publication number
- CN110633278A CN110633278A CN201910750618.2A CN201910750618A CN110633278A CN 110633278 A CN110633278 A CN 110633278A CN 201910750618 A CN201910750618 A CN 201910750618A CN 110633278 A CN110633278 A CN 110633278A
- Authority
- CN
- China
- Prior art keywords
- patient
- information
- user
- entry
- hospitalization
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The embodiment of the invention relates to a generation method of a patient hospitalization registry, which comprises the following steps: the method comprises the steps that a server receives a first form generation request sent by a user terminal of a first user; generating a first form according to the first table item and sub-table item information corresponding to the first table item, and sending the first form to a user terminal of a first user; a user terminal of a first user receives patient information input by the first user according to the first table item and the sub-table item information; the server determines a second user ID corresponding to the patient information according to the patient information in the first form; generating a second form according to the second table item and sub-table item information corresponding to the second table item, and sending the second form to a user terminal of a second user according to a second user ID; the user terminal of the second user receives the patient information input by the second user according to the second table item and the sub-table item information; the server generates a hospitalization registration table according to the first form of the patient and the second form of the patient and stores the hospitalization registration table in the hospitalization information registry.
Description
Technical Field
The invention relates to the field of data processing, in particular to a method for generating a patient hospitalization registry.
Background
In the information age, scientific data is called strategic resources. With the development of science, medical technology is also changing day by day. How to automatically and accurately acquire the related information becomes a problem to be solved in the technical field.
Disclosure of Invention
The invention aims to provide a method for generating a patient hospitalization registration form, which can be used for large-scale structural acquisition of relevant information, quickly and effectively forming a targeted information form, establishing an information base, providing ordered, standardized and shared information management for the relevant information and further better serving patients.
To achieve the above object, the present invention provides a method for generating a patient hospitalization registry, the method comprising:
the method comprises the steps that a server receives a first form generation request sent by a user terminal of a first user; the generation request includes a patient ID;
the form information corresponding to the generation request is determined in a form list; the form information comprises a form item and a sub-form item corresponding to the form item; the table entries comprise a first table entry and a second table entry;
generating a first form according to the first table item and sub-table item information corresponding to the first table item, and sending the first form to a user terminal of the first user;
the user terminal of the first user receives the patient information input by the first user according to the first table item and the sub-table item information;
updating the first form according to the patient information to obtain a first form of the patient;
the server determines a second user ID corresponding to the patient information according to the patient information in the first form;
generating a second form according to the second table item and sub-table item information corresponding to the second table item, and sending the second form to a user terminal of a second user according to the second user ID;
the user terminal of the second user receives the patient information input by the second user according to the second table item and the sub-table item information;
updating the second form according to the patient information to obtain a second form of the patient;
and the server generates a patient hospitalization registration table according to the first form of the patient and the second form of the patient, stores the patient hospitalization registration table in a hospitalization information registry, and sends the hospitalization registration table to the user terminal of the first user.
Preferably, the patient ID includes an item number, a clinic number, and a water flow number.
Preferably: the first table entry comprises a patient basic information table entry, an eye auxiliary examination information table entry, a registered doctor information table entry, a diagnosis information table entry and a follow-up information table entry;
the second entry includes a surgical information entry.
Preferably, the step of generating a first form according to the first entry and the sub-entry information corresponding to the first entry and sending the first form to the user terminal of the first user specifically includes:
the server obtains page size data of the user terminal of the first user, generates a first form according to the page size data of the user terminal of the first user, the first table entry and sub-table entry information corresponding to the first table entry, and sends the first form to the user terminal of the first user, so that the user terminal of the first user displays the first form to the first user.
Preferably, the generating a second form according to the second entry and the sub-entry information corresponding to the second entry, and sending the second form to the user terminal of the second user according to the second user ID specifically includes:
the server acquires page size data of the user terminal of the second user, and generates a second form according to the page size data of the user terminal of the second user, the second form and sub-form information corresponding to the second form;
and sending the second form to a user terminal of a second user according to the second user ID, so that the user terminal of the second user displays the second form to the second user.
Further preferably, after the first form is generated according to the first entry and the sub-entry information corresponding to the first entry and is sent to the user terminal of the first user, the method further includes:
the server receives the basic information of the patient, which is sent by the user side of the first user and corresponds to the basic information item of the patient, and generates a disease association request according to the basic information of the patient;
inquiring whether patient information corresponding to the basic patient information exists in a disease database according to the disease association request;
and when the patient visit information corresponding to the basic patient information exists in the disease database, updating the diagnosis information table entry in the first table and the sub-table entry corresponding to the diagnosis information table entry according to the patient visit information.
Preferably, after the server generates a patient hospitalization registry from the first form of the patient and the second form of the patient and stores the patient hospitalization registry in a hospitalization information registry, the method further comprises:
recording an update time of the patient hospitalization registry, generating the form ID according to the update time so that the patient hospitalization registry includes the form ID;
and generating a corresponding relation between the patient ID and the form ID, storing the corresponding relation between the patient ID and the form ID into the hospitalization information registry, and calling the patient hospitalization registry by the user according to the corresponding relation between the patient ID and the form ID.
Preferably, before the server generates a patient hospitalization registry from the first form of the patient and the second form of the patient and stores the patient hospitalization registry in a hospitalization information registry, the method further comprises:
generating prompt information for confirming the signature of a registered doctor;
and receiving feedback information of the confirmation signature of the registered doctor input by the user according to the prompt information of the confirmation signature of the registered doctor, and storing the patient hospitalization registration table into a hospitalization information registry according to the feedback information.
The embodiment of the invention provides a generation method of a patient hospitalization registration form, which can be used for large-scale structural acquisition of relevant information, quickly and effectively forming a targeted information form, establishing an information base, providing ordered, standardized and shared information management for the relevant information, and further better serving for patients.
Drawings
Fig. 1 is a flowchart of a method for generating a patient hospitalization registry according to an embodiment of the present invention.
Detailed Description
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
The method for generating a patient hospitalization registry provided by the embodiment of the present invention is implemented in a clinical data management system server, and is used for follow-up visit of a patient after the patient visits a doctor, fig. 1 is a flowchart of the method for generating a patient hospitalization registry of the present invention, as shown in fig. 1, the method specifically includes the following steps:
in particular, the first user may be understood as a medical staff member in a hospital or a staff member using a clinical data management system. When a patient is at an outpatient visit, if the patient meets the inclusion clinical data study criteria, the patient's hospitalization registry should be registered into the disease database. When the first user needs to collect the patient information for the hospitalization registration, a request for generating a patient hospitalization registration form needs to be input to a clinical data management system server (hereinafter, referred to as a server) through a user terminal so that the clinical data management system collects the patient information for the hospitalization registration.
The user terminal includes, but is not limited to, a computer, a mobile phone, a tablet computer, and other terminals having a network connection function. The generation request includes a patient ID including a medical item number, office number, and serial number corresponding to the patient.
specifically, a form list is stored in the server, and form information in the patient state information acquisition table after treatment is stored in the form list. The form information includes the table entry and the sub-table entry information corresponding to the table entry. The server determines the form information required for the current patient from the generation request in step 101 in the form list. The form information includes table entries and sub-table entries corresponding to the table entries. The table entry can be understood as classification entry information in the table. The entries may be divided into a first entry for a first user and a second entry for a second user based on the classification. Wherein the second user may be understood as a medical person performing an operation on the patient, in relation to the first user being understood as a medical person in a hospital or a person using a clinical data management system.
In one specific example, the first entry for the first user includes: a patient basic information entry, an eye auxiliary examination information entry, a registered doctor information entry, a diagnosis information entry and a follow-up information entry. The sub-entries in the patient base information entry include: name information sub-table entry, sex sub-table entry, birth date sub-table entry and medical record number sub-table entry; the sub-entries in the eye auxiliary examination information entry include: whether an eye auxiliary examination sub-table entry, a mydriatic refraction information sub-table entry, an eye fundus item information sub-table entry, a single A super information sub-table entry and an Optical Coherence Tomography (OCT) information sub-table entry are completed or not; the sub-entries in the diagnostic information table entry include: the method comprises the following steps that an intrabulbar space occupying pathological change information sub-table entry, a retinal detachment information sub-table entry, a diabetic retinopathy information sub-table entry, an age-related macular degeneration information sub-table entry, a high myopia information sub-table entry and a familial information exudative vitreoretinopathy information sub-table entry; the sub-table entries in the follow-up information table entry include: the follow-up time information sub-table item and the follow-up level information sub-table item. The second entry for the second user includes a surgical information entry. The sub-entries of the surgical information entries include: the operation date information sub-table entry, the operation duration information sub-table entry, the operation mode information sub-table entry, the retinal detachment external surgery detail information sub-table entry, the vitreous operation detail information sub-table entry and the tumor local resection detail information sub-table entry.
specifically, the server obtains the page size data of the user terminal of the first user, generates a first form according to the page size data of the user terminal of the first user, the first table entry and sub-table entry information corresponding to the first table entry, and sends the first form to the user terminal of the first user, so that the user terminal of the first user displays the first form to the first user.
The current form page may be a page for printing, or a page for displaying on a computer or other display device may be used, different pages have different page sizes, and the server needs to acquire size data of the current form page for convenient printing or output display. Because each different table entry and sub-table entry needs various word space and line space with different sizes when being displayed, different table entries and sub-table entries need to be arranged on a display page for the size data of different table pages, that is, a first table is generated and output according to the size data of the current table page and the table entry and sub-table entry information in the table information. In this case, the first form can be understood as an unfilled form, which is part of the patient's hospitalisation registry.
In a specific example, the server generates and outputs the specific arrangement in the first form according to the size data, the table entry and the sub-table entry information of the current form page, as shown in table 1 below.
Patient number/patient ID:
TABLE 1
specifically, the first form includes table entry and sub-table entry information. After the server generates and outputs the first form, the server obtains the individual patient information corresponding to the individual table entry and sub-table entry information that has not been updated in the first form.
More specifically, the manner in which the server obtains the patient information may be any one of the following two manners:
in a first manner, the server directly receives patient information entered by the first user through the first user's user terminal based on the list and sub-list information in the first list that has not been updated. In this process, the first user is required to enter all relevant patient information with respect to the entry and sub-entry information in the first form. It will be appreciated that entries and sub-entries in different first forms may be entered by different persons than the entries and sub-entries. For example, the entry of the registered doctor information in the entry is entered by the medical staff, i.e., the user, while the other contents of the entry may be entered by both the medical staff and the patient.
In the second mode, the server only needs to receive the basic information of the patient, which is sent by the first user through the user terminal and corresponds to the basic information item of the patient in the first form, or receive the patient ID, and then the server generates a disease association request according to the basic information of the patient or the patient ID and inquires whether the patient information corresponding to the basic information of the patient exists in the disease database according to the disease association request.
When patient visit information corresponding to the patient basic information or the patient ID exists in the disease database, the server generates patient information corresponding to the existing diagnosis information entries and sub-entries in the first form according to the patient visit information. That is, in this process, the patient information corresponding to the existing diagnosis information entry and the sub-entry is obtained by the server-associated disease database.
When patient visit information corresponding to the basic information or the patient ID of the patient exists in the disease database, and the patient information generated by the server according to the patient visit information does not meet the necessary filling table entry and/or the sub-table entry in the first form, the server generates prompt information for supplementing filling information, and prompts a user or the patient that the patient information corresponding to the necessary filling table entry and the sub-table entry in the first form needs to be supplemented.
When the patient visit information corresponding to the basic information or the patient ID of the patient does not exist in the disease database, the server generates prompt information for continuous filling, and prompts the first user to continuously input the patient information corresponding to other entries and sub-entries in the first form.
In a specific example, the server receives the basic information of the patient as "wangzhi, man, 50 years old, identification number xxx". The table entries that must be filled in the clinical registry include: a patient basic information table, a registered doctor information table, an eye auxiliary examination information table and a diagnosis information table. The server generates a disease association request according to the basic information of the patient, and inquires and acquires a diagnosis information table item of which the basic information of the patient is 'Wangzhi, Man, 50 years old and ID number xxx' and a plurality of pieces of patient information corresponding to the sub-table items according to the disease association request. And because the eye auxiliary examination information table entry in the table entry is also a necessary filling entry, the server generates prompt information of supplementary information of 'please continue to fill related necessary filling content', and the prompt information is used for the user or the patient to supplement the patient information in the table entry which is not filled and the related sub-entry thereof according to the prompt information of the supplementary information.
It is understood that both of the above ways may be that the server obtains the patient information. In the first approach, the server may obtain full patient information at once, but more information needs to be input by the first user. In the second mode, the server can obtain the patient information corresponding to a part of entries in the first form by associating the disease database, so that the burden of inputting a large amount of information by the first user can be reduced although the operation pressure of the server is increased compared with the first mode. The user can combine the advantages and disadvantages of the two modes to set the server to acquire the patient information in which mode according to the needs.
specifically, after the server acquires the patient information corresponding to the first form, the server updates the first form according to the patient information to obtain the first form of the patient. At this point, the first form of the patient may be understood as a first form that has been filled in. The first form of the patient includes a patient ID.
specifically, the server determines a second user ID corresponding to the patient information from the patient information in the first form. This process may be understood as a process of determining a medical professional performing an operation on a current patient based on patient information in the first form.
specifically, the server obtains page size data of the user terminal of the second user, generates a second form according to the page size data of the user terminal of the second user, the second table entry and sub-table entry information corresponding to the second table entry, and then sends the second form to the user terminal of the second user according to the second user ID, so that the user terminal of the second user displays the second form to the second user. At this point, the second form may be understood as an unfilled form, the second form being another part of the patient's hospitalization registry.
In a specific example, the server generates and outputs the specific arrangement in the second form according to the size data, the table entry and the sub-table entry information of the current form page, as shown in table 2 below.
TABLE 2
specifically, the second form includes table entry and sub-table entry information. After the server generates and outputs the second form, the server obtains the individual patient information corresponding to the individual table entry and sub-table entry information that has not been updated in the second form.
specifically, after the server acquires the patient information corresponding to the second form, the server updates the second form according to the patient information to obtain a second form of the patient. The second form of the patient can then likewise be understood as a second form which has already been filled out. The second form of the patient includes the patient ID.
specifically, the server generates a patient hospitalization registration table according to the first form and the second form, stores the patient hospitalization registration table in the hospitalization information registry, and sends the patient hospitalization registration table to the user terminal of the first user, so that the first user can check the patient hospitalization registration table through the user terminal, or call the patient hospitalization registration table from the hospitalization information registry according to the patient ID.
In some preferred embodiments, prior to storing the patient hospitalization registry of the patient to the hospitalization information registry, the server records an update time of the patient hospitalization registry and generates the form ID according to the update time such that the patient hospitalization registry of the patient includes the form ID. Then, the corresponding relation between the patient ID and the form ID is generated, and the corresponding relation between the patient ID and the form ID is stored in the hospitalization information registry so that the user can call the patient hospitalization registry of the patient according to the corresponding relation between the patient ID and the form ID. After generating the corresponding relationship between the patient ID and the form ID, the patient hospitalization registry corresponding to the patient ID can be maintained according to the patient ID, so that the patient hospitalization registry of the patient is more convenient to maintain and call.
In some preferred embodiments, after storing the patient hospitalization registration form of the patient in the hospitalization information registry, the server generates prompt information for confirming signature of the registered doctor, receives feedback information for confirming signature of the registered doctor input by the user through a mouse or a touch screen or a handwriting board according to the prompt information for confirming signature of the registered doctor, and stores the patient hospitalization registration form of the patient in the hospitalization information registry according to the feedback information. The feedback information for confirming the signature by the registered doctor can be understood as the signature of the doctor, and is used for storing the patient hospitalization registration table of the patient into the hospitalization information registry after the doctor confirms the contents in the patient hospitalization registration table of the patient.
The generation method of the patient hospitalization registration form can be used for large-scale structured acquisition of relevant information, quickly and effectively forming a targeted information form, establishing an information base, providing ordered, standardized and shared information management for the relevant information, and further better serving for patients.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above-mentioned embodiments are intended to illustrate the objects, technical solutions and advantages of the present invention in further detail, and it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (8)
1. A method of generating a patient hospitalization registry, the method comprising:
the method comprises the steps that a server receives a first form generation request sent by a user terminal of a first user; the generation request includes a patient ID;
the form information corresponding to the generation request is determined in a form list; the form information comprises a form item and a sub-form item corresponding to the form item; the table entries comprise a first table entry and a second table entry;
generating a first form according to the first table item and sub-table item information corresponding to the first table item, and sending the first form to a user terminal of the first user;
the user terminal of the first user receives the patient information input by the first user according to the first table item and the sub-table item information;
updating the first form according to the patient information to obtain a first form of the patient;
the server determines a second user ID corresponding to the patient information according to the patient information in the first form;
generating a second form according to the second table item and sub-table item information corresponding to the second table item, and sending the second form to a user terminal of a second user according to the second user ID;
the user terminal of the second user receives the patient information input by the second user according to the second table item and the sub-table item information;
updating the second form according to the patient information to obtain a second form of the patient;
and the server generates a patient hospitalization registration table according to the first form of the patient and the second form of the patient, stores the patient hospitalization registration table in a hospitalization information registry, and sends the hospitalization registration table to the user terminal of the first user.
2. The method of claim 1, wherein the patient ID comprises an item number, a clinic number, and a water flow number.
3. The method of claim 1, wherein:
the first table entry comprises a patient basic information table entry, an eye auxiliary examination information table entry, a registered doctor information table entry, a diagnosis information table entry and a follow-up information table entry;
the second entry includes a surgical information entry.
4. The method according to claim 1, wherein the step of generating a first form according to the first entry and the sub-entry information corresponding to the first entry and sending the first form to the user terminal of the first user specifically comprises:
the server obtains page size data of the user terminal of the first user, generates a first form according to the page size data of the user terminal of the first user, the first table entry and sub-table entry information corresponding to the first table entry, and sends the first form to the user terminal of the first user, so that the user terminal of the first user displays the first form to the first user.
5. The method according to claim 1, wherein the generating a second form according to the second entry and sub-entry information corresponding to the second entry, and sending the second form to the user terminal of the second user according to the second user ID specifically includes:
the server acquires page size data of the user terminal of the second user, and generates a second form according to the page size data of the user terminal of the second user, the second form and sub-form information corresponding to the second form;
and sending the second form to a user terminal of a second user according to the second user ID, so that the user terminal of the second user displays the second form to the second user.
6. The method of claim 3, wherein after the generating a first form according to the first entry and the sub-entry information corresponding to the first entry is sent to the user terminal of the first user, the method further comprises:
the server receives the basic information of the patient, which is sent by the user side of the first user and corresponds to the basic information item of the patient, and generates a disease association request according to the basic information of the patient;
inquiring whether patient information corresponding to the basic patient information exists in a disease database according to the disease association request;
and when the patient visit information corresponding to the basic patient information exists in the disease database, updating the diagnosis information table entry in the first table and the sub-table entry corresponding to the diagnosis information table entry according to the patient visit information.
7. The method of claim 1, wherein after the server generates a patient hospitalization registry from the first form of the patient and the second form of the patient for storage in a hospitalization information registry, the method further comprises:
recording an update time of the patient hospitalization registry, generating the form ID according to the update time so that the patient hospitalization registry includes the form ID;
and generating a corresponding relation between the patient ID and the form ID, storing the corresponding relation between the patient ID and the form ID into the hospitalization information registry, and calling the patient hospitalization registry by the user according to the corresponding relation between the patient ID and the form ID.
8. The method of claim 1, wherein before the server generates a patient hospitalization registry from the first form of the patient and the second form of the patient for storage in a hospitalization information registry, the method further comprises:
generating prompt information for confirming the signature of a registered doctor;
and receiving feedback information of the confirmation signature of the registered doctor input by the user according to the prompt information of the confirmation signature of the registered doctor, and storing the patient hospitalization registration table into a hospitalization information registry according to the feedback information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910750618.2A CN110633278A (en) | 2019-08-14 | 2019-08-14 | Method for generating patient hospitalization registration form |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910750618.2A CN110633278A (en) | 2019-08-14 | 2019-08-14 | Method for generating patient hospitalization registration form |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110633278A true CN110633278A (en) | 2019-12-31 |
Family
ID=68969863
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910750618.2A Pending CN110633278A (en) | 2019-08-14 | 2019-08-14 | Method for generating patient hospitalization registration form |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110633278A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106295102A (en) * | 2015-05-21 | 2017-01-04 | 杭州微云通信技术有限公司 | A kind of intelligent medical treatment system and method inviting patient based on medical personnel |
| CN106354511A (en) * | 2016-08-31 | 2017-01-25 | 杭州逸曜信息技术有限公司 | Auditing interface generation method |
| CN106599572A (en) * | 2016-12-12 | 2017-04-26 | 广州薏生网络科技有限公司 | Cloud department based on inpatient management and department member collaboration |
| CN107527307A (en) * | 2017-08-24 | 2017-12-29 | 杭州悦马爱赏科技股份有限公司 | Hospital admission management method, apparatus and system |
| CN108877909A (en) * | 2018-08-06 | 2018-11-23 | 四川互慧软件有限公司 | A kind of hospital care comprehensive management platform |
-
2019
- 2019-08-14 CN CN201910750618.2A patent/CN110633278A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106295102A (en) * | 2015-05-21 | 2017-01-04 | 杭州微云通信技术有限公司 | A kind of intelligent medical treatment system and method inviting patient based on medical personnel |
| CN106354511A (en) * | 2016-08-31 | 2017-01-25 | 杭州逸曜信息技术有限公司 | Auditing interface generation method |
| CN106599572A (en) * | 2016-12-12 | 2017-04-26 | 广州薏生网络科技有限公司 | Cloud department based on inpatient management and department member collaboration |
| CN107527307A (en) * | 2017-08-24 | 2017-12-29 | 杭州悦马爱赏科技股份有限公司 | Hospital admission management method, apparatus and system |
| CN108877909A (en) * | 2018-08-06 | 2018-11-23 | 四川互慧软件有限公司 | A kind of hospital care comprehensive management platform |
Non-Patent Citations (1)
| Title |
|---|
| 王爱云等: "住院病人信息自助采集系统", 《甘肃科技》 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220392644A1 (en) | Systems and methods for determining a wellness score, an improvement score, and/or an effectiveness score with regard to a medical condition and/or medical treatment | |
| Chavez et al. | Chat Generative Pre-trained Transformer: why we should embrace this technology | |
| US7705727B2 (en) | System, method, and computer program for interfacing an expert system to a clinical information system | |
| US20160042134A1 (en) | Method of calculating a score of a medical suggestion as a support in medical decision making | |
| WO2012160796A1 (en) | Medical information display apparatus, operation method and program | |
| US20070136090A1 (en) | System and method for macro-enhanced clinical workflow | |
| CN110010232A (en) | Region public health resources share cooperative system and method | |
| CN112331298A (en) | Method and device for issuing prescription, electronic equipment and storage medium | |
| Gunasekera et al. | High-resolution direct ophthalmoscopy with an unmodified iPhone X | |
| Yang et al. | Medication abortion through telemedicine: implications of a ruling by the Iowa Supreme Court | |
| JP2014203416A (en) | Waiting time prediction system | |
| JP2007094471A (en) | Medical examination support system, medical examination support device, and medical examination support program | |
| US20160378922A1 (en) | Methods and apparatuses for electronically documenting a visit of a patient | |
| US20210295963A1 (en) | Real-time interactive digital embodiment of a patient | |
| WO2018123791A1 (en) | Method, system and storage medium for recommending resource allocation to target subject | |
| JP2021136018A (en) | Support device, support system, support method, and program | |
| JP6512527B1 (en) | Telemedicine support system, medical institution computer, support organization computer, method executed by medical institution computer, and program | |
| CN110633278A (en) | Method for generating patient hospitalization registration form | |
| US20220208380A1 (en) | Medical care support device, operation method and operation program thereof, and medical care support system | |
| CN108206059A (en) | A kind of method and device of data processing | |
| CN105320846A (en) | Scoliosis clinical case follow-up visit system | |
| CN110619933A (en) | Method for generating eye patient condition questionnaire | |
| KR20160086123A (en) | Apparatus for Electronic Medical Record Providing | |
| CN110600089A (en) | Method for generating patient state information acquisition table after treatment | |
| US20230289537A1 (en) | System for rendering electronic medical record data and language interpretation data on disparate devices at a healthcare provider location |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191231 |