Demonstration of the regional component of EGISZ from KIR / RTK
An “ministerial” meeting was held today in Irkutsk, at which the heads of health care institutions were shown the regional component of EGISZ ( what is this? ) - a medical information system from Corporate Information Routines LLC (contractually from Rostelecom). According to the program of modernization of health care in the Irkutsk region for 2011-2012 (there are similar programs in every region), the implementation should be completed in December of this year.
The deadlines are very tight, and opinions about the hasty transition from the “inherited IIAs”, which the direct performers express, are not softer. But what we saw at the demonstration of opportunities made us look at this work more positively. In many ways, we are not changing the “awl on soap”, we are acquiring, along with a new platform, new opportunities that we could not dream of yesterday.
')
1. Module EMK + IEMK (electronic medical record)
2. Module "Central Archive of Medical Images (TSAMI)"
3. Module "Registry - patient portal"
4. Module "Registry - portal of public services"
5. Module "Registry - pre-registration management"
6. Module "Nosologic registers"
7. Example of creating an invoice for services
8. Single collection of reports
9. Analytics module
There are a total of 9 videos made not on the test version, but on the already completed implementation in the Trans-Baikal Territory. Before the videos, an introductory presentation on the structure of the IIA was given, I also attach it to the post
1. The solution is almost entirely in the cloud. Institutional servers serve as a gateway to medical VPN for doctors workstations. MIS services allow the doctor to save from any workflow outside the MIS, all work goes in the browser (Firefox is recommended), so Linux and servers can be used for servers and AWPs . In particular, AltLinux 6.0.Centaur preinstalled on PCs and servers supplied to us under the healthcare modernization program
2. For the time being, only 1 VPN channel has been established in the institutions . But the fact that at least 1 backup channel RTK and MIAC is needed is remembered, and within six months they promise to build such channels
3. Some time will have to work immediately in 2 MIS - the “old” and “new”, and duplicate all transactions until the institution is able to switch to the new IIA as a whole. Sadly, but no other way.
4. Since January 1, 2013, a refusal of 30,000 rubles is provided for the refusal to service a patient , in particular, the refusal to make an appointment with a physician or pediatrician via informat or the Internet. Proof in the search process
More information on the topic of implementation can be found in the library of documents on the implementation of EGISZ , on the actual situation with the on-site implementation in the VK group of the IT in Medicine community , and of course in the comments to the topic.
PS: there is no “IT in medicine” hub or a similar profile. Mb Should I ask to open such a hub UFO?
The deadlines are very tight, and opinions about the hasty transition from the “inherited IIAs”, which the direct performers express, are not softer. But what we saw at the demonstration of opportunities made us look at this work more positively. In many ways, we are not changing the “awl on soap”, we are acquiring, along with a new platform, new opportunities that we could not dream of yesterday.
')
1. Module EMK + IEMK (electronic medical record)
2. Module "Central Archive of Medical Images (TSAMI)"
3. Module "Registry - patient portal"
4. Module "Registry - portal of public services"
5. Module "Registry - pre-registration management"
6. Module "Nosologic registers"
7. Example of creating an invoice for services
8. Single collection of reports
9. Analytics module
There are a total of 9 videos made not on the test version, but on the already completed implementation in the Trans-Baikal Territory. Before the videos, an introductory presentation on the structure of the IIA was given, I also attach it to the post
What remained outside the framework of video demonstrations, but was voiced by representatives of the KIR, RTK and our medical information and analytical center:
1. The solution is almost entirely in the cloud. Institutional servers serve as a gateway to medical VPN for doctors workstations. MIS services allow the doctor to save from any workflow outside the MIS, all work goes in the browser (Firefox is recommended), so Linux and servers can be used for servers and AWPs . In particular, AltLinux 6.0.Centaur preinstalled on PCs and servers supplied to us under the healthcare modernization program
2. For the time being, only 1 VPN channel has been established in the institutions . But the fact that at least 1 backup channel RTK and MIAC is needed is remembered, and within six months they promise to build such channels
3. Some time will have to work immediately in 2 MIS - the “old” and “new”, and duplicate all transactions until the institution is able to switch to the new IIA as a whole. Sadly, but no other way.
4. Since January 1, 2013, a refusal of 30,000 rubles is provided for the refusal to service a patient , in particular, the refusal to make an appointment with a physician or pediatrician via informat or the Internet. Proof in the search process
More information on the topic of implementation can be found in the library of documents on the implementation of EGISZ , on the actual situation with the on-site implementation in the VK group of the IT in Medicine community , and of course in the comments to the topic.
PS: there is no “IT in medicine” hub or a similar profile. Mb Should I ask to open such a hub UFO?
Source: https://habr.com/ru/post/161107/
All Articles