ჰაჰაჰა ზურა, ჩაგეთვალა!!! ხვალ შეგეხმიანები, მეც დავიკარგე ცოტა ამ მიმოწერებში

კი გადამინერგეს  :D თქვენ რას შვებით ნერგავთ?

ოკ ალექს

ზური როგორ ხარ? ღვიძლი ხომაა ფორმაში J

ეს შესაბამისობები ხომ გავაკეთეთ, ეხლა რაზეა საუბარი ვერ ვხდები. ქეთი ჩამოვა ხვალ და მას დაელოდეთ მომდევნო კომუნიკაციებზე.

ალეკო

Zura,

                Thank you, this solution works great for us. We can send you your ICD-10 codes using the list diagnosisCodes.

Right now we have 290 diagnosis to be transferred from HMIS into EIDSS. So, considering that the list of diseases can grow I would suggest to limit number of codes to 500.

Please let us know when this method will be available for testing.

Thanks!

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Andrey,

                Sorry for the late answer..

As we, with Vaja have discussed, the filtration may happen by the list of ICD10 Codes (Because they are universal Unlike ID - s), this will search for any occurrence of current codes in any  of the Case’s Diagnoses (which may’ve been registered by both ICD10  and  Artificial Code), and it may have some quantity  limit for the codes that are passed as parameters (this restriction will just protect the service from any unnecessary load.. please provide the maximum number of such diagnosis so that we can limit it that way), it will look like this:

CasesResultContract GetAllCasesByDateRangeAndDiagnosis(Guid loginToken, DateTime startDate, DateTime endDate, List diagnosisCodes)

and

please tell us what you think

Thanks,

Zura

Zura,

                Could you please let us know your thoughts on two questions below?

                We have a tough schedule and would like to resolve any technical issues as soon as possible. Thank you.

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Zura,

                Thank you. We can now see a few test cases you created on July 8.

                What would be the best way for records filtration to reduce a server load? We think the easiest way is to create a method CasesResultContract GetAllCasesByDateRangeAndDiagnosis(Guid loginToken, DateTime startDate, DateTime endDate, Array diagnosisID) which take an array of your diagnosis GUIDs as an input parameter and returns all cases where at least one of the diagnosis in your case exists in the provided array. Please let us know your thoughts.

Also we would like to have more records for our tests. Could you please let us access more records.

Thanks.

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Andrei

 I've checked the service and if the values are passed as I've provided, it returns proper results, if you're having problems getting data please provide the values which are passed as parameters for this method.

 As for the data filtration, I’m sure we can find a way to filter data before it is passed by desired diagnosis to minimize the load on both sides  (it may be ICD10 Code or some additional info);

Now the system takes about 2500 - 3000 cases per day total

If you’ll have any questions or technical issues please let us know

Thanks,

Zura

Zura,

                We have troubles with getting your data again. The system returns no records for any filter dates. Could you please double check it?

                Also we have a question regarding the method “GetAllCasesByDateRange”. Your method doesn’t allow to filter records by diagnosis, so we have to retrieve all cases for the last month, however only some cases with a specified diagnosis should be imported from HMIS to EIDSS. Could you please let us know how many cases on average you have in HMIS for one month as well as the average size of a case? Ideally it would be nice to have a way to retrieve only those records which match the provided list of diagnosis as a filtration criteria. If it’s not possible we need to know the mentioned above numbers to plan the server load on our side.

I copied our IT expert Andrey Vdovin for further direct communication.

Thanks!

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

You are welcome Andrei

Zura,

                Thank you for the explanation. At this point it’s not an issue for us.

                We’ll continue with our tests and let you know if we have any questions.

                Thank you!

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Andrei,

Thanks for the mail.

For testing purpose, please could you use dates Zura provided. After we will make real connection from your side, system will give data for larger date

Have a nice day,

Best Regards,

Alexander

Alexander Turdziladze

Chief of Party

Abt Associates Incorporated - Georgia

USAID Health System Strengthening Project
A. Tsereteli ave. #144 16^th FL. Tblisi Georgia

Tel. (995 32) 510021 Ext.#1617
Mob: +995  593 226226

Dear Andrey,

                As I mentioned, period is considered to be less than a month, this is because of the big amount of data stored in our system ;

using real database, one year period could mean half of a million cases (~538 000), requesting all of them at once will eventually eat up all of the server memory and CPU  resources,

if one year period data is necessary for one request, you could call the same method for each month separately.

For testing purposes (also for real data) this restriction should not cause you any problems;

Thank you

Zurab,

                Thank you, it works fine with your dates, but if we select a larger date range (like 1 year from now) the system gives an empty list.

Are there any restrictions for the date range we should know about?

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Andrey,

It depends on what values are passed for date time parameters , for ex. period is considered to be less than a month,

You could use these values for first test: startDate:  7/6/2014 1:14:00 PM; endDate: 7/8/2014 5:14:00 PM (month/day/year)

thanks

Zurab,

                Thank you. We don’t have an error message now but the system gives us an empty list.

Also, could you please make sure that test records contain all data fields, so we can check that all data variables are properly transferred.

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Greetings Andrey,

You can call the service method “GetAllCasesByDateRange” now, we have also created some test cases (using todays  date/time range as creation date);

Thanks,

Zura

Dear Andrey,

I am cc my colleagues in correspondence. They will contact shortly.

Thanks,

Alexander

Alexander, Ketevan,

                Thank you for the link.

We were able to access your service and login in. However when we call method “GetAllCasesByDateRange” according to your instructions the system says: “Access denied”.

Could you please double check it and also create some test data in your system so we can do more tests. Thank you.

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Dear Natalia,

Thank you very much for your mail.

Please see attached, service description document. As Ketevan mentioned in her previous mail, service indeed is slightly modified version from previous one, we provided long time ago to establish connection between two systems. Hope B&V IT team will not have problems using it. To access the service, please use following information.

User: eidss

Pass: @eidss_123456@

Please could you let us know, when  technical work will be finished from B&V side. In that case, we will register test data in our system for data exchange purpose.

Have a nice day,

Best Regards,

Alexander

Dear Natalia,

Thank you for your email. We are glad to see that technical work is progressing and we’ll be able to complete the integration soon.

Let me inform you that your inquiry was discussed with the MoH and as agreed, we will provide you the access credentials and all other essential details. We do not expect that this service will be different from what we shared earlier, but before sending it, let us once again have a look at the service structure and get back to you early next week.

Respectfully,

Dear Aleko and Keti,

To continue technical works on HMIS – EIDSS linkage, we would like to kindly ask you to provide us with access to your integration web service connected to a test database. We will require a link to the web service and login data.

We would like to start looking at the way your service operates and begin testing of the integration: for these purposes, several cases will be required to be present in your test database.

Please let us know when we can receive this information from you.

Thanks in advance,

Thank you Andrey!

Please let us know if we can support technical work for connection process.

Best Regards,

Alexander

Dear Ketevan,

                Thank you for the provided information!

1.       As we discussed, if NCDCPH is ok with having just a current resident address, it works fine for us too.

2.       Thank you for the specification. For the field “Final status” which is still marked as outdated we’ll use the following values you provided us earlier: 1 -Total Recovery; 2 -Life Functionality Recovery; 3 -Stabilization; 4        -Remission; 5 -Lethal; 6 -Referral To Stationary hospital; 7 -Referral To same hospital Branch or department; 8 -Referral To Ambulatory hospital; 9 –Continues. Please confirm this is a correct list.

3.       We’ll try to match geo references by Georgian names you provided and let you know how many variances we get.

Sorry for a delay in response and thank you again!

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Dear Andrey and colleagues,

Per our latest agreement, sending you the requested documents. Also, would like to clarify couple points.

1.      Registration address: patient’s registration address stored in CRM database comes automatically from the Civil Registry Agency (CRA), after patient’s synchronization with the CRA. However, the data is not yet standardized and at this point represents a string, a text separated by commas. HSSP has no control over the format and completeness of the information coming from the CRA. Meaning that in certain instances we may not be able to provide a complete address, as it might be missing in the CRA database itself. Nevertheless, the module includes a set of fields (region, municipality, etc.), which were put in advance with the assumption that the CRA would be able to provide a full set of data in the near future. Some of these fields might be empty now, but having them shall guarantee compatibility between two systems (CRA/HMIS), when address fields are standardized on the CRA side. At this point, they are working to resolve this issue, however we don’t yet know when this activity is completed.

Earlier, per your request, we added patient’s current address, which is both structured and standardized. We can certainly share the registration address, but given its unstandardized format, plus the fact that registration address is not an absolute must for the EIDSS (as confirmed during our last discussion), we would recommend to stick with the current address only. Also, please note that current address fields are not mandatory at this point, however we can make sure that every time system encounters a disease code that is reportable to EIDSS  - these fields become mandatory. So, as soon as the final list of diseases is available, it will take us less than a day to reflect this logic. Therefore, would like to kindly ask to confirm whether this suggestion is acceptable for you or not.

2.      Web-Service: no changes were made into the web-service since you last received it, so the one you have is the most recent. However, if we decide to eliminate the registration address, then we will have to remove the field highlighted in yellow (please, refer to the WCF document attached) .

3.      References for regions, municipalities, etc: in another attached document, you will find the hierarchy of regions, settlements and other, including their IDs. As mentioned earlier, unfortunately, we are not able to provide this list in English, as well as GIS coordinates.

Besides the list of diseases, that is to be discussed with the NCDCPH, are there any other outstanding issues we can help with?

Looking forward to your feedback,

Sincerely,

Dear Andrei,

Thank you very much for your comments.

Of course we will do maximum efforts to have as maximum compatibility between two systems as it will be possible, but I would like to suggest to use HMIS to get information as Notification regarding Case for notifiable diagnoses approved by MOH and after EIDSS users can fill out all required info. If we will use this concept, I think it make connection easier and it is enough to have information only regarding;

1.      Patient ID

2.      Patient Name

3.      Patient Surname

4.      Diagnose

5.      Health Care Provider patient gets treatment

Once again I want to stress that this is my personal opinion. I think this issue can be decided during next meeting between NCDC & DTRA

Please see my comments bellow in red color and also in attachment.

Have a nice weekend,

Beset Regards,

Alexander

All,

                Thank you for the feedback, we are making some progress!

At this point we have just two issues:

1)      Some fields from original dataset are still missing in the web service, e.g. out of two patient’s addresses (current and registration) the only current address is available. Please find details attached.

The provided HMIS web service specification refers to the “Outcome\Final Solution” variable as outdated which is not used anymore. However in the response below it’s proposed to use this variable. So, if the provided specification is not correct can we have the correct one?

Field “Outcome” is now filled by latest specification and indicates final outcome of the case

2)      Since the web service doesn’t provide lists of available reference value we need to agree how we can get them. We added the list of diagnosis (the latest version after our previous discussions) to the attached specification for easier reference. It still requires a review and clarifications. As for regions, rayons and settlements references, we don’t have them at all. If these lists are available it would be nice to have them attached to the specification.

Please see attachment regarding settlement list – I hope B&V local office can help in translation.

Hope we can resolve as many tech issues as we can before the joint call.

Thank you.

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Dear All,

Please see bellow my comments (in red color) related to questions raised by Andrei (I prefer, to make more detailed discussion during the meeting)

Also please see attachment in which we made comments related to missing or corresponding data.

We are ready to attend meeting, next week convenient time for you – I would like to ask NCDC organize meeting and express their position on different topics to have final decisions.

Best Regards,

Alexander

Natalia, I think this is a great suggestion. My recommendation is not to do a technical discussion over the conference call. Let’s agree on all technical points in this email distribution and then hold a finalizing Meeting/Call. Again – this is only a recommendation.

V/R

Paata

Dear all,

I would also like to thank everyone for involvement and reviving the discussion on this important topic.

Unfortunately, I am unavailable for meeting this week and will be out of town till Wednesday next week.

Having said that, I would like to suggest the following: there are two technical points that require response from HMIS team (Andrey’s email points 2 and 3) - these could be addressed in written via this chain of emails and the response would give better ground for further joint discussion. We could meet at the end of next week (a call-in option shall be required for B&V tech team participation) to discuss outcomes for the two technical questions and one administrative question that will require NCDC participation.

Please let me know if this works for everyone.

Thank you,

Dear All,

Thank you very much for your involvement. It is good idea (necessary) to organize meeting and discuss all details related to connection.

I would like to ask to set time the end of this or beginning of next week.

Looking forward for the meeting.

Best Regards,

Alexander

Dear Brian, Paata,

First of all, I would like to thank you and all participants sides for active cooperation.

As you know, for the National Centre for Disease Control is very important the integration of the two systems (HSSP&EIDSS), so we are actively involved in the meetings, which will be devoted to discussion of the raised issues.

We hope that at the meetings we will find solutions to settle these three issues.

Sincerely,

Ekaterine Kavtaradze

National Center for Disease Control

and Public Health (NCDC) of Georgia

Deputy General Director

9, Asatiani str

0186, Tbilisi Georgia

Tel: (99532) 31-17-54 ext: 202

Fax: (99532) 31-17-55

E-mail: e.kavtaradze@ncdc.ge

www.ncdc.ge

Aundrei,

Thank you for the information. Sounds like B&V is close to having everything needed to perform the integration. Recommend a meeting among B&V, HMIS, and NCDC technical SMEs to discuss the three issues below to come up with recommendations for each.

Kind Regards,

Brian

Brian, Paata,

                The approach proposed by HMIS works fine for us in general. However there are some issues which have to be addressed before this approach can be utilized for the integration. Please find them below:

1)      The list of variables to be transferred from HMIS to EIDSS was agreed with NCDC. The proposed web service doesn’t provide all of them (missing fields marked with yellow background in the attached specification).

The absence of some variables does not prevent the integration but it needs to be discussed with NCDC to setup right expectations, e.g. NCDC expected to get information regarding the women mortality but the web service doesn’t provide it.

Please see attachment, in which we made comments regarding missing or corresponding data.

To get women mortality It is possible to use following fields from web service;

-         Patient’s Gender – Women

-         Patient’s Age – it is possible to filter any age, for example 15-49 or any other combination

-         Outcome

Soon, we are planning together with MoLHSA, NCDC and Ministry of Justice replace current Vital Registration system and it will allow us technically provide information regarding dead women’s who are registered not only in case registration module, if MoLHSA will give us green light on that.

2)      There is one critical for the integration variable which we cannot find in the web service: rayon\district of the current residence of a patient. Cases cannot be transferred from HMIS into EIDSS without  a proper identification of a patient’s address.

We made comments in attached file

3)      Some variables contain reference values (marked with red color in the attached specification), e.g. list of diagnosis, regions, rayons, settlements. The web service doesn’t provide lists of available reference values which is critical for the integration.

Reference values can be delivered in the following ways: (1) as a part of documentation and (2) as a part of the web service. Option 1 requires starting the discussion between EIDSS and HMIS teams after every change in reference values. Option 2 (commonly used integration approach) provides a way of on-line access to the actual list of reference values and doesn’t require further discussions.

We made comments in attached file

                So, we are ready to move forward with the proposed approach after resolving the issues mentioned above.

                Should you have any questions, please let us know. Thank you!   

Best Regards,

Andrey Oukharov, Ph.D.

Black & Veatch | Cooperative Biological Engagement  Program

16 Marksistskaya St., 109147 Moscow, Russia

+7 495-232-6738  p| +7 916-605-9893  m| oukharov@bv.com

Dear Brian, Paata,

I am sending service description document for 3^rd option connection. We are ready to answer all questions raised during revision process from B&V

Have a nice day,

Best Regards,

Alexander

Dear Brian,

Thank you very much for your response. Yes you are absolutely right, we propose 3^rd option. Maximum next week B&V will have all technical details and service description to review.

Best Regards,

Aleko

Dear Aleko,

Thank you for the below info. I think it is unavoidable to lengthily write about this integration since there are so many nuances. You capture them well. So it sounds like what you have done is proposed a 3^rd option. Please ensure that B&V has the 3^rd option and its technical details so that they can review.

Kind Regards,

Brian

Dear Brian, Paata,

Thank you very much for your email. Let me first express my huge gratitude and appreciation to DTRA and DTROG for the invaluable assistance you provide to Georgia.

We also highly appreciate your cooperation with our project and wish to have long-term and closer relationships with you in future as well. We truly believe that our collaboration will guarantee receipt and generation of better quality information by the Government of Georgia, Ministry of Labor, Health and Social Affairs (MoLHSA) and NCDC&PH and support to prudent decision making based on accurate data. We hope that your interventions will not only support specific components but the HMIS as a whole, which will include different systems in future.  I believe that the Stock Management module, which is currently being implemented at NCDC&PH, is a very good example and a prerequisite of successful cooperation between us, despite the fact that we do not have any contractual relationships and/or funding; however, we think that our joint work on development of different criteria for the Stock Management system was very fruitful and can lead to future successful joint projects.  

As for the HMIS/EIDSS connection, we perceive its importance really well and accordingly, our team did its best and made maximum efforts to ensure this connection happen. From our side, data were transferred from the real HMIS database to the EIDSS test database. We consider that if there is a connection between the EIDSS and the HMIS it will ensure sustainability and stability of the EIDSS and the Ministry will be able to maintain this system together with the HMIS even after DTRA funding ceases.

But, before I answer your questions and share our point of view regarding the options of B&V connection, let we briefly review some key aspects of the HMIS per your request,  that may be partially known for the persons involved in this correspondence. I believe, this review will help answer questions that might have aroused during the collaboration process between the HSSP and the B&V.

Development of the HMIS with assistance of the USAID Health System Strengthening Project (please note that the product is owned by the Ministry), started in Y2011 and the first product was the Case Registration module, implemented in Spring 2011 (the module to which the EIDSS is to be connected). Nowadays, HMIS counts more than 20 modules and increasing (you can view the list of all products at www.ehealth.moh.gov.ge). HMIS is used by the Ministry of Labor, Health and Social Affairs to execute various key functions, namely: collect medical statistical data and information on financial liabilities in real-time mode, enabling instant responses from the MoLHSA side and many more. But most importantly, MoLHSA executes financial transactions to healthcare providers through the HMIS. That said, it can be concluded that the financial incentives, along with various administrative sanction measures, are the main factors for effective functioning of the system. As of today, 99 % of providers (hospitals and PHC units) are users of the HMIS. It should also be emphasized, that in the very near future 2 more modules will become effective, that are of special interest to EIDSS, namely: TB management module (that covers patient management process from the very first contact) and vital registration (registration of death and birth events), that soon shall replace the currently existing vital registration system of the Ministry of Justice. The latter shall collect all birth and death cases in Georgia, including the medical and other reasons of death.

Besides the health service providers, HMIS also incorporates various State and non-State stakeholders. Online service connections are made with various parties, which are not part of the HMIS, in particular:

·         All beneficiaries (individuals) are identified and verified with the Service Development Agency of the Ministry of Justice

·         All healthcare providers are identified and verified with the National Agency of Property Registration (i.e. the Public Registry)

·         Connection with the Customs Department of the Revenue Service for import/export management of pharmaceutical products

·         With private insurance companies

·         With pharmaceutical companies and pharmacies

And other stakeholders, including Ministries, listing of which will take us too far.

Abovementioned service connections enable us to receive standardized citizens’ related information and similarly for organizations, pharmaceutical products, insurance status and so forth, which is a pre-defined and common standard used in the Country by the key stakeholders (i.e. data sources); consequently, when we transfer data from the HMIS we use the same standardized format. So, this is to mention that data exchange is a common and widely used practice in HMIS, as you can judge based on the number of parties we receive or exchange information.

So, to receive and send data, we use standard web services, which come with detailed description of fields and web service methods. When we receive data (when the data source is outside the HMIS), on our side we ensure all technical works, including all the necessary logics and validations. In contrary, when we transfer data outside the HMIS, meaning that the HMIS is the source of the data, other systems ensure relevant technical preparatory interventions, to set up the required logic and validation on their side. Having said that, we envisage the connection with EIDSS in a same manner, which is absolutely similar to the approach we use with other parties.

The proposed options below were discussed with the IT Department of the MOLHSA. IT department as mandated by the First Deputy Minister, is now in charge of assessing all IT systems in healthcare sector in terms of protection of confidentiality and security of patient proprietary and other information. I have copied Mr. Mikheil Janiashvili, the head of the IT department of the MoLHSA, who can confirm the Ministry’s position on this topic. As for the options:

1. Option I - "HMIS creates views in their database according to the attached specification and provides access to these views to EIDSS" - Ministry is against doing this type of connection, because it means that we will have to grant access to whole patient data we have in HMIS, and this violates the confidentiality requirements.

2. Option II - "HMIS creates an Open API component for data retrieving and filtering according to the attached specification and provides access to this component to EIDSS" - HSSP has estimated work requested by B&V and it is much complicated and requires much more efforts compared to earlier request to send filtered data using special algorithms to EIDSS.

However, As I have mentioned above, instead of 2 scenarios above, HSSP is offering to B&V using web services prepared by our team; meaning that for every notification case to be  transferred to EIDSS, our team will provide complete set of required and available information regarding the case. B&V, in its turn, can use this information according the format they wish. We will send documentation along with the service description.

Finally, please accept my apologies for such along letter; however, I considered myself obliged to provide you with details in order you could draw unbiased/objective conclusions. 

And it is needless to mention that we are ready for any discussion that may help push this process further.

Looking forward to successful cooperation in future,

Respectfully,

Aleko

Alexander Turdziladze

Chief of Party

Abt Associates Incorporated - Georgia

USAID Health System Strengthening Project

A. Tsereteli ave. #144 16th FL. Tblisi Georgia

Tel. (995 32) 510021 Ext.#1617

Mob: +995  593 226226

-----Original Message-----
From: Enukidze, Paata [mailto:EnukidzeP@state.gov]
Sent: Friday, January 10, 2014 6:31 PM
To: Alexander Turdziladze (aturdziladze@hssp.org.ge); Alexander Turdziladze
Cc: Enukidze, Paata; Huether, Brian M; Papelova, Natalia; Schiller, Alexander CIV (alexander.schiller@DTRA.MIL); Cardenas, Leonardo A. MAJ USAF; McLellan, Krystal M; Hall, David CIV; Oukharov, Aundrei (AO); Christopher.Thompson_Contractor@dtra.mil; Wahl, Tom (T); ეკატერინე ქავთარაძე; პაატა იმნაძე
Subject: HMIS - EIDSS Integration Proposal

Dear Aleko, can you please let us know what is your recommendation back to us, based on the below options given by our EIDSS SMEs concerning the automated integration of HMIS System module with EIDSS. The options below consider a new approach towards making the connection to work in an automated manner. Considering that the connection is deemed as very important by our program, we propose to you to give us your position on the options below and let us know if there is yet a different approach more acceptable and workable by both sides on this matter.

I also appreciate your explanation of the process your (HMIS) data goes through and how it is monitored for accuracy. I understand that the HMIS database is nation-wide and many times falls in the category of confidential information. Please feel free to let us know if we are going to inherit similar approach towards the shared data if our two systems were to link up, understanding that this may be a question to MOH or NCDC rather than to HMIS team. 

We appreciate your cooperation and long-term commitment to work with our program continually to make the system do better using your data, which I hope is eventually what NCDC and GOG can benefit from. And thank you for the conversations on this subject we held for the last few days.

Thanks again

Paata Enukidze

Assistant Chief/Project Coordinator

DEFENSE THREAT REDUCTION OFFICE – GEORGIA United State Embassy, Tbilisi enukidzep@state.gov; 995 599 60-76-42;

Recommendation for Integration Options:

Please find the proposal for the integration between HMIS and EIDSS involving case data transferring from HMIS to EIDSS.

The integration can be done on EIDSS side with a minimum contribution from the HMIS team. This scenario only requires HMIS to provide an access to their data according to the attached specification. All algorithms for data retrieving, filtering, synchronization and processing in a proper way will be done on EIDSS side.

The attached specification contains the description of datasets which EIDSS has to have an access to:

-          tab "Case Data" - information regarding actual case records in

HMIS database;

-          tabs 1-12 - information regarding the actual reference values

utilized in HMIS database, including list of diagnosis and healthcare providers.

The access to the required dataset can be provided by the following means:

1.       HMIS creates views in their database according to the attached

specification and provides access to these views to EIDSS;

2.       HMIS creates an Open API component for data retrieving and

filtering according to the attached specification and provides access to this component to EIDSS.

Both options work for EIDSS, but we believe option 1 will be easier for HMIS to implement.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.

This message may contain privileged and confidential information intended solely for the addressee. Please do not read, disseminate or copy it unless you are the intended recipient. If this message has been received in error, we kindly ask that you notify the sender immediately by return email and delete all copies of the message from your system.