Code Monkey home page Code Monkey logo

handsbox's Introduction

handsbox

Folder-based Electronic Forms Records for Kentucky HANDS Program.

In order to use the HANDS Box, you will need:

  • A file share for storing charts and working files. If you can set up or have access to a secure web server, you might consider:

    • Nextcloud or Owncloud
    • Otherwise, you will likely need to use a regular Windows file share, using a Windows file server connected to your domain, or a Samba based file server.
  • If you choose to store the charts and working files on a Windows file share, you will need to install a tool to keep your files in sync, such as one of these:

  • You will need a good PDF reader / editor capable of:

    • Filling PDF forms
    • Saving filled forms
    • Digitally signing documents
    • Capturing and affixing signatures from participants (optional)

This has been tested with the following:

Quick Start

  • Download the latest HANDS Box Release.zip from Releases
  • Extract the zip file to your local machine. The configuration assumes placing HANDS Briefcase inside your Documents folder.
  • If you're using Nextcloud, place the contents of HANDS Briefcase into your Nextcloud folder.
  • If using a Windows File share, the scripts assume you will map the network drive to H:
  • Open HANDS Documents\Software\hands_defaults.ini
    • Uncomment relevant lines and adjust paths for your environment.
  • Open HANDS Documents\Software\updateinstall.cmd
    • Change paths to match your environment.
  • Use FreeFileSync to "Edit" the Sync HANDS Box.ffs_batch file. Adjust according to your environment.
  • Run updateinstall.cmd to install the HANDS Box into your %appdata% path.
  • Launch HANDS Box from the new Desktop shortcut.
  • Answer the questions to set the mode, then re-launch the HANDS Box.
  • Experiment by creating labels, forms, packets, and "queueing" to different staff.

Video Demos

  • See the Video Demos page for a visual demonstration of using the HANDS Box.

Software Overview and Tools

Folder Structure

On each laptop, there should be a folder structure something like this.

  • Documents\HANDS Briefcase
    • Charts.Region1
    • Charts.Region2
    • HANDS Documents (synced down from server)
    • Forms
      • English
        • ABC 101 - Parent Entry Form [A].pdf
        • ABC 102 - Parent Exit Form [A].pdf
        • ADM 100 - Entry Packet [A].txt
      • Spanish
      • billingcodes.txt
    • Software
    • Supervision Forms
    • Working.MyWindowsUsername (two-way synced with server)
      • Labels
      • Needs Correction
      • To Data Processing
      • To Supervisor
      • Tracking Form
      • Work In Progress
    • Working.OtherHomeVisitor
    • Working.MoreStaff
    • Working.Etc.

Synchronize files using a service like Nextcloud or Owncloud. The GroupFolders app in NextCloud is an excellent option for sharing charts.

Alternatively, set up a file share on a central server and map to each client laptop, e.g.

net use H: \\server\HANDS /persistent:yes

Working folder names should exactly match the usernames of the logged in users on each laptop

Staff should have full read-write permission to their own Working Folders, and permissions to other working folders and charts as necessary for accessing data for processing, supervision, etc. Most staff should have read-only access the HANDS Documents folder to prevent accidental changes to software and templates. It is suggested that the compiled HANDS Box software be distributed through the HANDS Documents folder.

Creating PDF Templates

PDF Templates are regular, fillable PDF documents. Special fields that will be pre-filled from the "label" should be named EXACTLY as follows:

  • _LCDHD_FSW (Home Visitor's Full Name)
  • _LCDHD_SSN (Patient ID or SSN)
  • _LCDHD_CLID (Clinic ID)
  • _LCDHD_DOB (Patient Date of Birth)
  • _LCDHD_LNAME (Patient's Last Name)
  • _LCDHD_FNAME (Patient's First Name)
  • _LCDHD_MI (Patient's Middle Initial)
  • _LCDHD_BILLING (Billing Code)
  • _LCDHD_NAME (Patient's Full Name)
  • _LCDHD_FORMDATE (Date of Form)

PDF Templates should be named with the following convention:

FORM NUMBER - Form Title (Form Date) [CODE].pdf

Building the software

In order to build the software, you will need to download and install AutoIt, install other prequisites, and compile.

Find details under BUILDING

Latest Changes

Find a list of latest changes in CHANGLOG

handsbox's People

Contributors

fiforms avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.