CHI electronic policy API

Question

Java

At the moment, in some regions of the Russian Federation, a compulsory medical insurance policy can already be obtained in the format of a smart card (this may not mean that it is easy to do, insurance companies still oppose progress and by hook or by crook force their customers to receive paper mugs). But the infrastructure, nevertheless, is gradually being improved, and readers for policies have finally been sent to the hospital for which I wrote the system for the emergency room.
The barcode reader has already been connected, since the kit included a data unpacking library, but there was a hitch with electronic policies.

In general, to the point of the issue, the reader came with a set of dlls written in .Net and, in addition, obfuscated by trial Spices.Net. It was not possible to obtain additional information from the local Foms members. It is known that the card works in the PC / SC standard, which is supported by java starting from 1.6, but it was not possible to quickly understand the set of commands that can pull out the necessary information from the policy. Does anyone have any information about the existence of a java incarnation of this library, or where can I find a more low-level interface (that would be even better)? Naturally, no one is going to transfer the system to .Net, but it would be necessary to connect the reader.

Answer 1

Apparently I will answer to myself, but oh well, let it be, suddenly someone else will be interested.
The library still succumbed to reversing under the debugger, but to a limited extent, although sufficient to implement the plan. The most important thing that we managed to get out of the library is the field codes along with the names and requests / responses in their raw form. Raw data is relatively easy to decode, since UTF-8 was used to save strings. I would also note perhaps saving dates in the form 0xDD 0xMM 0xYY 0xYY, I probably wouldn’t have had enough imagination for such :) The data structure, in principle, is quite logical and natural (header with code and data length, then the data itself is encoded depending on the type of topics or otherwise), although some things remained beyond my understanding, such as some sortable fields that I never saw, or the first byte of the field header, the meaning of which remained a mystery to me.
I don’t see much point in publishing the resulting library, because it won’t be difficult to repeat my path.

Answer 2

Is the topic alive?
Is the author tracking it?
You may ask, how is the situation with reading the electronic CHI policy now?

Answer 3

Nobody wants to make normal services in the Russian Federation, so far there are only supposedly such https://oms-policy.rf