- 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:
Open questions:
- could performer/asserter be the user that is logged in to the system or another one?
- Could transaction consist of resources for different patient or not?
- Is there a limit for resources number in one transaction?