Dear Ketevan,

 

Good to hear from you and no problem about delayed reply. We are happy that we are able to move forward.

 

Attached please find the contract proposal in word format.

 

Best regards,

Tuomas

 

 

Dear Tuomas,

 

I am sorry for late reply. By Georgian reregulation, contract must be both in English and Georgian languages. If you have word version of the contract please send us in it is possible.

 

With best regards,

 

Keti

 

 

 

Dear Ketevan,

 

Did you have a chance to go through the contract and do you find that it is ready to be signed as is?

 

Best Regards,

Tuomas

 

 

Dear Jussi,

 

We will send you ICD, NCSP and DRG groups name in Georgian and of the next week. Also about test data, It and UHC department ask you send us again format of test data and detail definition of this format.

 

Are you using Cyrillic alphabet of Unicode like sylfaen?  

 

We will send you information about contract on Monday.

 

Also I send you IT departments questions:

 

-         According documentation there are three possible requestor (like VisualDRG, WebAPI and File Grouper) to database which should be provided from your side for setting up DRG. Should we consider that database for all of them (VisualDRG, WebAPI and File Grouper) and should it be located in one physically server.

-         In ‘DRG Grouping’ section, we have ‘Revenue’ field. How this value is calculated?

-         In software price list, ‘VisualDRG’ does not have version. Do you mean Professional or Standard?

-         Should we have possibility to use Georgian user interface in ‘VisualDRG’. If so, what are the instruments that we should use for translations?

-         Does ‘VisualDRG’ support Windows 10 (both x86/x64)?

-         In previous email we asked regarding Main and Secondary diagnosis in web API. How can we pass diagnoses so your system can separate and recognize main and secondary diagnoses?

-         In our ICD10 classification system asterisk-dagger codes are little part of whole list of the ICD10 codes.

o   How can we pass those pairs to Web API? How will the Web API distinguish those pairs?

o   Is there the same 20 x 2 diagnoses and 20 procedures limit in Web API as is in Visual DRG Grouper file (Appendix C)?

o   Are there different instructions for passing asterisk-dagger and other (no asterisk and no dagger)  ICD10 codes to the Web API?

o   What is the instructions for writing nonasterisk and nondagger ICD10 codes to Visual DRG Grouper file (Appendix C)?

-         Do we have Unicode (utf8) support in VisualDRG, WebAPI, File Grouper and their database? In our case, it is critical because all data tracked in our systems and databases are in utf8 format.

-         We already have document „Prodacapo_Grouper_REST_API_general_description.pdf„ for web API. Should we consider methods and parameters given in document as a latest version or you are going to provide updated one with ‘VisualDRG Setup Kit’ (as you mentioned it previous mails)?

-         According your request to provide test data, we recognized that you are asking us indicate Actual cost of the case. As we clarify given, information is not requested to generate DRG code. In that case, what is the main purpose of this field?

-         In ‘Appendix C: File format for DRG case data’ description, what is the relation among diagnoses and procedures fields? Are there any strict rules to put related piers of diagnoses and procedures in same logical positions? Also, is there any rules to indicate that some diagnoses are Main and other should be considered as secondary?

-         In “Prodacapo_Grouper_REST_API_general_description.pdf” document the response  of https:///evdrgwr/api/v1/drg API method contains “genderFlags, ageFlags, dischargeStatusFlags, lengthOfStayFlags, diagnosesFlags and proceduresFlags”. What do these fields mean?

 

Thank you in advance,

 

With best regards,

 

Keti

 

 

 

Hello!

 

Now descriptive texts for diagnoses and procedure in the tables are in English.

 

Is that OK for you? Those texts will be used in VisualDRG only as helper texts when entering diagnosis and procedure codes and do not affect anyhow actual grouping results.

 

If you wish to have diagnosis and procedures in VisualDRG in Georgian language, we need those texts in files (Excel with code and texts in separate columns). Those may require extra work from us (Cyrillic alphabet) but we do not know before we test those.

 

Also, could You provide a test data file to be used for our testing and to be included as a demo data file in VisualDRG setup kit.

 

Best regards,

Jussi