CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • Community Sponsored Improvements (Moderator: Donald Lobo) »
  • Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....
Pages: [1]

Author Topic: Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....  (Read 2393 times)

ngingras

  • I’m new here
  • *
  • Posts: 15
  • Karma: 0
Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....
January 02, 2010, 04:28:52 pm
I work for a nonprofit organization that delivers services both directly and indirectly to seniors. We use CiviCRM for most aspects of client interaction except for service delivery. Our existing service tracking software is expensive, inflexible, proprietary, poorly supported, poorly documented, there's no community to speak of, and if I'm completely honest - it's mostly rubbish.

What this software does that Civi doesn't is allow us to schedule and record the delivery of specific services to specific clients. We can define types of services which can be linked to different providers and funding sources so that at the end of each reporting period we can provide outcomes data to our funders. One twist is that we'd almost certainly have to duplicate one of the surprising strengths of our existing software: the ability to interact with touch screens and bar code scanners. We use this in certain situations where the client records their own services.

Here's what we need to be able to do with "CiviServe":

- Define types of services and link them to to contacts configured as funding source(s) and service provider(s)
- Define which types of organizations, volunteers, etc can provide specific services
- Define eligibility requirements for specific services (demographics, location, etc.)
- Create custom fields for services to record additional details. (like "meal type" for a meals on wheels service, etc)
- Schedule people to receive services, and assign the service to available organizations, volunteers, etc.
- Record contacts who've been denied access to services (including notes, reason for denial, etc.)
- Record the delivery of scheduled services (including batch entry)
- Display history of services on each contact's profiles
- Report outcomes by funding source, provider, date ranges, demographics, underserved, overserved, etc.
- Solid import/export capabilities for interacting with other systems which are often required by various funders.

And of course some modifications to CiviCRM in general:

- Integration of CiviServe with existing search, reporting, custom data, profiles, etc.
- Ability to create touchscreen and barcode scanner friendly profiles for kiosks and mobile phones
- Email notifications when activities and services are scheduled or assigned

The question is who would be capable of taking this on, and what kind of development resources are necessary for such a large project? For us to fund a substantial project isn't inconceivable given the cost of what we're currently using.

-n8

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....
January 03, 2010, 10:40:52 am
Based on your high-level requirements list, I would say that the existing CiviCase component functionality meets about 50% of your requirements (Services = Cases). If you haven't spent some time reviewing (and potentially playing with) CiviCase - that would be a good next step:

http://wiki.civicrm.org/confluence/display/CRMDOC/CiviCase+Admin

Then we should schedule a conference call to dig into more details in terms of requirements, resources and timing. Ping me directly - dave at civicrm dot org - to schedule this. Provided the funding is there, the core team can potentially take on a chunk of the development, assuming we are generalizing things enough to make this useful for a range of service delivery / management settings. To get a bit of perspective on funding requirements, we usually estimate that development of a 'small component' for core takes ~200 hours. Our rate sheet is here:

http://wiki.civicrm.org/confluence/display/CRM/CiviCRM+Consulting+Rate+Sheet
Protect your investment in CiviCRM by  becoming a Member!

ngingras

  • I’m new here
  • *
  • Posts: 15
  • Karma: 0
Re: Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....
January 03, 2010, 11:00:53 am
Thanks for the response. We did play around with CiviCase when it was first implemented (around v2.1 or so) with the intention of trying to use it to collect service data but found it kind of a stretch and maybe even a little too complicated for what we were looking to do.

Perhaps the biggest obstacle at the time was that configuring it meant writing or at least copying and modifying configuration files. Though maybe this has changed and we need to take another look. We did have some uses in mind for CiviCase for programs that function in a manner consistent with CiviCase's workflow, but for general service delivery we more or less just need something like a simple POS-type system.

Again, thanks for taking the time to reply. Based on your rates, I think that we could justify sponsoring the lion's share of the development IF we could replace our existing database. But we will spend some time exploring the functionality of CiviCase in the latest CiviCRM release before we go any further.

Cheers,

-n8
« Last Edit: January 03, 2010, 11:02:35 am by ngingras »

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Discussion (deprecated) »
  • Feature Requests and Suggestions »
  • Community Sponsored Improvements (Moderator: Donald Lobo) »
  • Inquiry: CiviServe Module, and Touchscreen Friendly Profiles....

This forum was archived on 2017-11-26.