From : Järveläinen Jussi <Jussi.Jarvelainen@prodacapo.com>
To : Ketevan Goginashvili <kgoginashvili@moh.gov.ge>; Maia maglakelidze-khomeriki <Mmaglakelidze-khomeriki@ssa.gov.ge>; itabatadze@ssa.gov.ge; srostiashvili@ssa.gov.ge; Serpola Pekka <Pekka.Serpola@prodacapo.com>
Subject : Georgian DRG questions: version-id and DRG point price in VisualDRG
Cc : Ketevan Goginashvili; Maia maglakelidze-khomeriki; itabatadze@ssa.gov.ge; srostiashvili@ssa.gov.ge; Serpola Pekka
Received On : 22.01.2019 13:42

Please could someone from Georgia confirm (Accept or otherwise) that this time slot is ok for You.

Agenda

Agree on the following DRG grouper questions:

1. What would be for you a good logic version-ID of this grouper?

o Is GEO2018PR1 or GEO2019PR1 better?

o Standard version ID is: ++<PR for Production versions>+1, 1b,…2 in case of definition table changes during the year>.

o Technically we need to select one equally for all the products using the same logic version.

2. What would be for you a good default value used in VisualDRG for cost of DRG point (GEL / point)?

o Some technical default is required and this can be changed in VisualDRG by yourself.

o We have now used technical placeholder value 200 GEL / point, which results in (now we have a copy of Latvian weights as agreed on, which doesnt match 1:1 with Georgian DRG groups, also this can be updated later) for example for hip-surgery (ICD=S324 and NCSP=NEJ50) that would result in DRG 211N which has weight 1,6514 in Latvian weight table: 1,6514 x 200 = 330,28 GEL, which is quite low, as calculated DRG revenue in VisualDRG.

o Having good default value is recommended but not compulsory. Normally weight 1,0 should reflect average cost of all ward encounters based on some reference data set. Technically, this is not a requirement.

3. Other questions

· Status of new definition tables from NCC and potential open issues in those (if any)

.........................................................................................................................................

Join Skype Meeting

Trouble Joining? Try Skype Web App

Help

[!OC([1033])!]

.........................................................................................................................................