- Transaction is designed to create resources in e-Health as a single atomic operation (all or nothing).
- Transactions follow FHIR approach for transactions.
- As for now with the help of transaction could be created all resources that are connected with medical events
- All resources have the reference to patient inside.
- All resources are saved to DB separately and in addition the signed document is stored in a document storage as a whole.
- There is no route to get or update original transaction, but there's a route to get the transaction response.
- Transactions are asynchronous and follow FHIR approach for async processing.
Transaction validations
- Validate access_token;
- Validate scopes. There should be validation for transaction:write and for each resource in the transaction validation should be performed (encounter:write, observation:write, etc.);
- Validate DS.
...