- Transaction is designed to create resources in e-Health.
- As for now with the help of transaction could be created all resources that are connected with medical events
- All resources have the patient_id inside
- All resources are saved to DB separately, but saved all together in the data storage, as the are signed with one DS
- there is no rout to get or update transactions
Transaction validations
- Validate access_token
- Validate scope
- validate DS
Validations of:
| Question | Decisions History | |
|---|---|---|
| 1 | Is it allowed for a signed transaction to contain resources produced by other employees (where resource's performer/asserter isn't equal to the given user) | Yes. The transaction is signed by one employee and may contain resources produced by employees from the same legal entity (14.11.2019). |
| 2 | Could transaction consist of resources for different patient or not? | No, currently transaction only support resources for a single patient (14.11.2019). |
| 3 | Is there a limit for resources number in one transaction? | Yes, there should be a limit. The exact amount is TBD (14.11.2019). |