Delivery Activity
Was this helpful?
User Guide
Was this helpful?
A Delivery Activity is the technical output of a delivered service; it essentially represents each delivered service to each . It is very unlikely that the average end user (or ) will need to be concerned with these records, as it is a fairly technical record. The information captured on a Delivery Activity will include the following key information:
Key Dates
A reference to the which delivered the service to the
A reference to the Item funding the delivered service for the
Billing information to ensure Maica's billing engine can process the delivered service
Let us further explain this via an example:
If an is scheduled to deliver occupational therapy to 2 , the will have two Delivery Activities, one for each Participant for the service.
Each Delivery Activity will be billed according the underpinnig the service for each .
The purpose of Delivery Activities is to track delivered services and create a billing record that can be processed by Maica's billing engine. This essentially abstracts the from the billing and allows administrators to manage specific billing scenarios as required by any relevant business process.
Delivery Activities are a backend process and get generated when scheduling Appointments to deliver services to Participants. The Maica billing engine then reads the Delivery Activities to inititate the appropriate billing logic.
The generation of Delivery Activities is totally controlled by Maica, there is no reason to manually interact interact with these records. You are able to change them in case the billing logic execution produced incorrect results but, outside of this use case, these will just run in the background.