Case Management Flashcards
Case
Case = interaction between participant and SPM org.
Contains information on participants who want to receive the benefit or service, information on others involved, evidence, eligibility decision information, financial transactions, comms, notes, events.
Case triggers sequential chain of events/case lifecycle
Case Types
Differ by when and where they are used in the case lifecycle 7 types are: Screening Assessment Application Integrated Product Delivery Issue Investigation
Screening Case
First-level, used to handle and store several program specific assessment cases.
Evidence for multiple assessments can be entered at this level.
Can get evaluation of eligibility for multiple programs
Assessment Case
Determine potential eligibility for a benefit or service
Can determine potential eligibility for an individual program without creating a Product Delivery Case
Each case represents a program/product
Each case has a rule set assigned to it, to determine eligibility
Application Case
Captures Client’s initial application for benefits and services, such as household members, evidence
Usually includes: Client applying, evidence required, and information relating to application (date etc)
Can be created online via online application
Contains any programs client is applying to
After eligibility check, case can trigger creation of Integrated case and one or more Product Delivery Cases
Integrated Case
Like a screening case, as acts as container for consolidating information
Used to consolidate case information for one + participants
Used as a folder to store and manage multiple cases of any type for one or more members of a household/family
Once created has the status of open. Lifecycle incl. Open and Closed
Each case in Integrated Case has its own Lifecycle
Product Delivery Case
Determines whether participant meets actual eligibility criteria for single benefit/liability product
Contains functions needed to manage delivery of product
Each PDC has rule set assigned to it, to determine actual eligibility
Eligibility determination usually results in benefit or bill being delivered
Benefits delivered to persons in ongoing monetary payment
Liabilities delivered in form of a bill
Issue Case
Used to capture and manage differences in evidence & info received from participant/3rd party
E.g. reason for leaving different from employers
In ongoing case maintenance, supply info to org to aid reassess of eligibility.
Issue types are templates on which issue cases are based. Usually named for type of evidence collected
Issue Resolutions - mark end point or decision at conclusion of issue. “Agree with Client” “Agree with Employer”
Issue Resolution Approval Checks - can configure issue cases to manual or auto approval
Investigation Case
Inquires into circumstances of allegation/incident
e.g. child abuse, fraud
Can record all relevant details that concern any type of investigation
Info recorded: interviews, assessments, notes, comms
Provide org with info to complete findings, record decision, and resolve
Features/Functionality: allegations, findings (founded/unfounded), resolutions, action plans, milestones, contacts, translation requirements, history
Workflow of Delivering a Benefit
- Submit Application Form (Client/ Caseworker submits)
- Check for Eligibility (Application cases checked & authorized)
- Cases Created if Eligible (creates Integrated & PDC)
- Submit Additional Evidence
- Submit PDC for Approval
- Activate PDC
- Issue the Payment
Case User Roles
- Case Owner = responsible for case info and maintenance, can be any of the following org objects (user, position, org unit or work queue).
- Case Supervisor = responsible for reviewing and approving cases that are submitted for approval.
- Case Reviewer = responsible for periodic review of PDC’s.
- When you create a case, SPM automatically assigns a Case Owner, default is the same user who registered the first participant added to the case, namely the Primary Case Participant. Same for all case types except for Issue Cases.
- An Admin can associate a case type with a case-ownership strategy process. When a case is being created, if a case-ownership strategy workflow process is associated with the case type, the initial case owner is determined by using the workflow process. If not, the sample out-of-the-box algorithm is used.
- A Supervisor Role can be assigned to a case manually or automatically, so they can action approval requests for the case. The reporting hierarchy in the org. structure determines the automatic assignment of a Supervisor, which is set up in the SPM Administration Manager. A supervisor is dynamically assigned only when an action requiring Supervisor intervention on a task/notification is performed on the case.
- The Case Reviewer Role is responsible for performing periodic reviews on a PDC. Case reviews can be set manually as a case event or scheduled at a regular frequency, as determined in Product Administration. By default, the Case Reviewer is the same as the Case Owner.
Case Tabs & Sections
- Home-Case Details –display summary details about a case, e.g. creation/start dates, objectives, status of the case. CaseHeader is the name of the data model entity (database table) that stores high-level info about a case.
- Participants–all those who play a role in the case e.g. other household members are a Case Member in an application group.
- Contact–contain details of user-entered notes, attachments, records of meeting minutes, records of communications.
- Events (calendar)–individual milestone of significance to a case, system can automatically create events as a result of case processing or manually created by a user. Case closure event is an example of an event that the system creates. Can manually create these events; meetings, reviews, referrals and activities.
- Tasks–an instruction to carry out an item of work, user manually creates tasks or system can auto create tasks. Tasks that relate to a case can be viewed and maintained from the case task list.
- Issues and Proceedings –can include issue cases with evidence, investigation cases into allegations, appeal cases of cases or determinations, legal actions by courts, and special cautions or warnings about participants.
- Administration–this tab provides links to information on related cases, transaction history, and user roles for the case.
Specific Case Tabs & Sections
Integrated Case Specific Elements:
- Evidence –the PDC within the Integrated Case uses evidence associated with the Integrated Case.
- Services –lists all service records on the specified case, provides links to view and edit these records.
- Referrals –List including the clients that were referred, the provider they were referred to, who referred them and the referral date.
- Outcome Plans –Used to manage activities designed to address the client’s circumstances, to achieve a specific goal, e.g. self-sufficiency.
Specific Case Tabs & Sections
Product Delivery Case Specific Elements:
•Determinations –contains one or more decisions defining the client’s eligibility and entitlement for one or more components within a product.
•Financials
–Transactions are the payments and bills issued for eligible and active PDCs.
–Certifications are the eligibility periods for products.–Deductions are money subtracted from benefit payments.–Components represent the various categories of payment for a product.
–Delivery Patterns consist of delivery method (cash, EFT) and delivery frequency (weekly, monthly) of payments.
–Nominees are the recipients of benefit payments.–Over and Under Payments if too much or too little is paid out on the case.
–Payment simulations show all payments and deductions due to a participant for a specific date before the payment is issued.
Application Case Lifecycle
Each stage has a Case Status, indicating the stage and deciding which stage it moves to next
•Only applications with a status of In Progress or Submit Failed can move into a state of Submitting.
•A case status history is maintained for an Application Case throughout its lifecycle.
stages:
•Creation
•Approval
•Cancellation
•Determination
•Disposal