Abstract: The present disclosure relates to server and a method for vendor-independent acquisition of medical data by health care units. The method comprises transmitting request to a cloud database by the server at predefined intervals of time. The request comprise list of one or more medical devices associated with one or more subjects of the health care unit. Further, the server obtains medical data of the one or more subjects from the cloud database based on the request and correlation of the medical data with medical device data. Upon receiving the medical data, Device Message Layer (DML) communication session is established with a data manager of the health care unit by the server and the medical data is transmitted to the data manager through the established DML communication session by the server for vendor-independent acquisition of the medical data by health care units. Figure 4
Claims:We claim:
1. A method for vendor-independent acquisition of medical data by health care units, comprising:
transmitting, by a server associated with a health care unit, request to a cloud database at predefined intervals of time, wherein the request comprise list of one or more medical devices associated with one or more subjects of the health care unit;
obtaining, by the server, medical data of the one or more subjects from the cloud database based on the request and correlation, performed by the cloud database, of the medical data with medical device data , wherein the cloud database receives the medical data from one or more user devices associated with the one or more subjects;
establishing, by the server, a Device Message Layer (DML) communication session with a data manager of the health care unit; and
transmitting, by the server, the medical data to the data manager through the established DML communication session for vendor-independent acquisition of the medical data by health care units.
2. The method as claimed in claim 1, wherein the one or more user devices receives the medical data from the one or more associated medical devices of the corresponding one or more subjects, manufactured by vendors, using a mobile application of the corresponding vendor of the one or more medical devices.
3. The method as claimed in claim 1, wherein establishing the DML communication session comprises implementing, by the server, a Point of Care Report Generator (POCRG) interface for the one or more medical devices.
4. The method as claimed in claim 1, wherein the one or more medical devices are registered with the cloud database and the server by providing at least one of the medical device data and subject data.
5. The method as claimed in claim 4, wherein the cloud database correlates the medical data with the medical device data based on the registration.
6. The method as claimed in claim 4, wherein the subject data comprises details of each of the one or more subjects as per records in the health care unit of the subject and unique ID assigned to the one or more subjects by the health care unit.
7. The method as claimed in claim 1, wherein the medical device data comprises serial number, vendor identification number, model number, manufacturer name and medical device name of each of the one or more medical devices.
8. A server for vendor-independent acquisition of medical data by health care units, comprises:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
transmit request to a cloud database at predefined intervals of time, wherein the request comprise list of one or more medical devices associated with one or more subjects of the health care unit;
obtain medical data of the one or more subjects from the cloud database based on the request and correlation, performed by a cloud database, of the medical data with medical device data, wherein the cloud database receives the medical data from one or more user devices associated with the one or more subjects;
establish a Device Message Layer (DML) communication session with a data manager of the health care unit; and
transmit the medical data to the data manager through the established DML communication session for vendor-independent acquisition of the medical data by health care units.
9. The server as claimed in claim 8, wherein the one or more user devices receives the medical data from the one or more associated medical devices of the corresponding one or more subjects, manufactured by vendors, using a mobile application of the corresponding vendor of the one or more medical devices.
10. The server as claimed in claim 8, wherein the server implements a Point of Care Report Generator (POCRG) interface for the one or more medical devices to establish the DML communication session.
11. The server as claimed in claim 8, wherein the one or more medical devices are registered with the cloud database and the server by providing at least one of the medical device data and subject data.
12. The server as claimed in claim 11, wherein the cloud database correlates the medical data with the medical device data based on the registration.
13. The server as claimed in claim 11, wherein the subject data comprises details of each of the one or more subjects as per records in the health care unit of the subject and unique ID assigned to the one or more subjects by the health care unit.
14. The server as claimed in claim 8, wherein the medical device data comprises serial number, vendor identification number, model number, manufacturer name and medical device name of each of the one or more medical devices.
Dated this 01st day of September, 2016
R RAMYA RAO
OF K & S PARTNERS
AGENT FOR THE APPLICANT
, Description:FIELD OF THE DISCLOSURE
The present subject matter generally relates to field of health care. More particularly, but not exclusively, the present disclosure discloses a server and a method for vendor-independent acquisition of the medical data by the health care units.
| # | Name | Date |
|---|---|---|
| 1 | Form 5 [01-09-2016(online)].pdf | 2016-09-01 |
| 2 | Form 3 [01-09-2016(online)].pdf | 2016-09-01 |
| 3 | Form 18 [01-09-2016(online)].pdf_20.pdf | 2016-09-01 |
| 4 | Form 18 [01-09-2016(online)].pdf | 2016-09-01 |
| 5 | Drawing [01-09-2016(online)].pdf | 2016-09-01 |
| 6 | Description(Complete) [01-09-2016(online)].pdf | 2016-09-01 |
| 7 | REQUEST FOR CERTIFIED COPY [02-09-2016(online)].pdf | 2016-09-02 |
| 8 | Form 26 [02-09-2016(online)].pdf | 2016-09-02 |
| 9 | Other Patent Document [23-09-2016(online)].pdf | 2016-09-23 |
| 10 | abstract 201641029903 .jpg | 2016-10-03 |
| 11 | Form 3 [28-12-2016(online)].pdf | 2016-12-28 |
| 12 | 201641029903-PETITION UNDER RULE 137 [23-03-2021(online)].pdf | 2021-03-23 |
| 13 | 201641029903-OTHERS [23-03-2021(online)].pdf | 2021-03-23 |
| 14 | 201641029903-FORM 3 [23-03-2021(online)].pdf | 2021-03-23 |
| 15 | 201641029903-FER_SER_REPLY [23-03-2021(online)].pdf | 2021-03-23 |
| 16 | 201641029903-DRAWING [23-03-2021(online)].pdf | 2021-03-23 |
| 17 | 201641029903-COMPLETE SPECIFICATION [23-03-2021(online)].pdf | 2021-03-23 |
| 18 | 201641029903-CLAIMS [23-03-2021(online)].pdf | 2021-03-23 |
| 19 | 201641029903-FER.pdf | 2021-10-17 |
| 20 | 201641029903-PatentCertificate29-11-2023.pdf | 2023-11-29 |
| 21 | 201641029903-IntimationOfGrant29-11-2023.pdf | 2023-11-29 |
| 22 | 201641029903-PROOF OF ALTERATION [14-03-2024(online)].pdf | 2024-03-14 |
| 1 | SS_201641029903E_28-09-2020.pdf |