Event (events)

Solve Care decentralized platform persists data on Nodes, computes and makes its available on a time series based on Events. The platform is built around processing events. Each Event is anchored on Blockchain with complete auditability on event timeline. In Care.Protocol an Event is the most important component to configure as any Network participant role would either be producing or consuming an event. For example – A Doctor sending prescription to a patient is an event. Every Event has an originator in form of Card on Wallet or Node. Events are consumed by Wallet and Node

Field Name Value Type Description
id Number 1. Unique event id across the network.
2. Auto generated
3. Required
name/code String 1.Name of the event
2. Required
description String 1. Description of the event
2. Required
type String 1. Type of the event:
a. Wallet Event
b. Node Event
2. Required
card String 1. Card reference ID.
2. Required
from_role String 1. Event producer role.
2. Required (If 'type' is Node event)
to_role String 1. Event recipient role.
2. Required (If 'type' is Node event)
status String 1. Event status:
a. Active
b. Inactive
2. Required
version Number 1. The Version of the event. (This version updates in an event of a change of the role metadata values.)
2. Required
event_definition_ref String 1. Event payload definition JSON reference. (This definition consists of event payload fields and constraints.)
2. Required
3. JSON file – event_definition.json
wallet_event_handlers Array 1. List of wallet event handlers for this event. (It consists of wallet internal event handlers and incoming event handlers.)
2. Required (If 'type' is wallet event)
node_event_handlers Array 1. List of node event handlers for this event. (These are outgoing event handler – node events.)
2. Required (If 'type' is node event)
next_event String 1. Next event
2. Required
exclusive_consent_needed String 1. The event specific consent needed from the event consumers. By default, NO. Override it incases event attached with consent.
2. Optional

Note:

    1. Node Events
      1. Node Event Handlers
    2. Wallet Events
      1. Wallet Event Handlers