---
# System prepended metadata

title: Digimed (#dragonfly project) vs orders and BI reporting

---

# Digimed (#dragonfly project) vs orders and BI reporting

## Where we are now, in brief?

- we're about 80-85% done
- preparing for the deadline (Dec 12, next Monday)
- backend - we're good, frontend - a bit struggling

## As far as orders and BI is concerned....

- what we have (the flows) are, as of now, completely not connected to orders/compensations. I assume you'd like us to integrate digimed/Dragonfly code to orders & compensations

- some of the DB fields (like ICPC2 code) will be encrypted in the database side, and therefore not available in PowerBI (technically they will be fetchable, but they'll contain encrypted gibberish)

- until orders/compensations are integrated to Digimed, I shall have a basic Excel report for you, somewhat resembling the one we did for Falcon (the one for Municipality), to give you feedback. Between 12 Dec and 1 Jan i don't think there will be any meaningful data anyways, so that should suffice.

The columns in report would include:
- ConsultationID
- consultation creation time (when it was either created automatically from Pridok, or customer created it via Wizard himself)
- wait time (diff between creat and start time, [min.])
- consultation start time
- consultation end time
- duration in minutes
- patient name
- user_id (of a patient)
- doctor name
- doctor_id
- consultation outcome (referred_gp, helped, unable_to_help)
- ICPC2 code 

**if I forgot about sth important - please let me know**

## Big questions

Can we agree, we're going to have a separate product for Digimed consultation?

#### #1 How to integrate orders to digimed Consultations?

**OUR OPTIONS:**

**OPT #A** - We create a new order, for every Digimed consultation

**OPT #B** - Consultations are "packed" into orders, in bulk, eg. 1 order per week, or 1 order per month.

#### #2 How to construct the automatic pricing for these orders?

I don't really know any specifics aside from the fact that the price will be somehow connected to the time customer waited for the doctor (SLA)








## Notes 2022-12-12