Unlike most challenges here, this one is about speed, not just correctness. It asks DM practitioners to implement the same decision service using their favorite BR&DM tool and report its actual execution time.
The problem. A company that used SQL against a database for its medical services decided to migrate to a serverless architecture. The first microservice, “Determine Medical Service Coverage,” looks up coverage attributes for a medical service using a single (large) decision table with 16,369 rules covering combinations of medical-service characteristics.
Expected solution. Build a RESTful decision service that accepts a medical service description in JSON and fills in its coverage attributes. Run it against 10 provided JSON test cases and report the average execution time per request, excluding network overhead — ideally by deploying the service so anyone can call it directly (e.g. from Postman) to reproduce the numbers.
Send your solutions to DecisionManagementCommunity@gmail.com, or open a pull request to add yours here.
One submitted solution (Prolog, by Matteo Redaelli) was originally published as an external write-up whose link no longer resolves. If you’re the author (or know a working link), please open a pull request adding the
urlfield back.