We'll see throughout this training that NEO's structure affects the reports you're able to create.
The three most important objects in NEO are: Clients, Transactions and Items.
Some data is collected about the client as a person. Some data is collected about the transaction that the client has with the service provider (aka the contact, visit, encounter). Transactions contain items like needles and kits, or services and referrals.
Clients have attributes like their client reference code, year of birth, registration date and various demographics. Transactions have attributes like the the date and location of the transactions. Items have attributes like the item's name (e.g. stericup, counselling) and type (e.g. cooker, service).
A simplified illustration of NEO's data structure is below. NEO includes a lot more data than what you see here, but this is the most important relationship to understand when making sense of your data.
How is a client created?
Clients are only created when you register a new client reference code in NEO, e.g. MAKO1993 (Female).
What about anonymous clients?
In addition to real client records, NEO has placeholder client records to represent anonymous clients, e.g.:
- Anonymous (Man)
- Anonymous (Woman)
- Anonymous (Trans Man)
- Anonymous (Trans Woman)
Whenever you log an anonymous transaction, that transaction is associated with one of these placeholder clients.
What about bulk entry?
In some situations, you might use the Client Count module to log that multiple clients received some items/services.
In the example below, the entry would be logged as "Anonymous (Male) participated in 100 individual transactions." Of the 100 individual transactions, 75 would contain 1 nasal naloxone kit and 25 would contain 1 injectable naloxone kit.
You enter the number of clients and the gender.
Then enter how many items were distributed to that group of clients. In this case, 100 male clients received 75 nasal naloxone kits and 25 IM naloxone kits.
