ApplicationForm
Name Health eTouch ED
Aliases Health eTouch 2.5
BUSINESS INFO - - - - - - - - - - - - - - - - - - -
Short Description Administers patient surveys via a kiosk in the ED setting
Purpose Administers patient surveys via a kiosk in the ED setting
Business Owner Joe Gregory, Randy Smith
Primary Users Patients, DeptEmergency?
Data Contents PHI
Access Channel(s) Intranet
VENDOR/SUPPORT INFO - - - - - - - - - - - - - - - - - - -
Technical Support Contact(s) AndyFox? , EricKramer? , BenRidout?
Technical Support Info

Vendor(s)

TECHNICAL INFO - - - - - - - - - - - - - - - - - - -
Application Type(s) Client, Server, Integration/Messaging
Implementation Languages,
Frameworks, Tools
FrameworkDotNet? , LanguageVB? , FrameworkWebServices? , ToolBatchAndPrint?
Dependencies

Monitoring status In need of monitoring

Version Control Information

Assets for this project are located, in general, beneath the http://restfs:8080/tfs/Health eTouch 2.5 folder. The table below outlines specific locations within TFS for the various individual Health eTouch components.

Application Component Purpose TFS Location
Windows Client solution Application that is installed on the kiosk PCs http://restfs:8080/tfs/Health eTouch 2.5/eTouchSurveyClient.root
Service: eTouchSurveyRetrievalService Server-side service providing customized survey to client http://restfs:8080/tfs/Health eTouch 2.5/eTouchSurveyRetrievalService.root
Service: eTouchSurveyResponseService Server-side service recording survey responses captured by client http://restfs:8080/tfs/Health eTouch 2.5/eTouchSurveyResponseService.root
Service: PatientDemographics? Server-side service providing basic demographics to client

=http://restfs:8080/tfs/Patient Demographics

Environments

This section details the different environments available for the application. Having segregated environments allows multiple versions of our systems/applications to be used concurrently.

Development Environment(s)

Overview

  • Web Services
    • Server - ServerRESC3DEV
    • Directory - \\resc3dev\c$\Inetpub\wwwroot\eTouchWebServices
  • Client
    • Andy's workstation
  • Deployment Steps

Web Service Deployment

  • Deploy codebase to eTouchWebServices folder beneath webroot ( c:\Inetpub\wwwroot\eTouchWebServices for dev)
  • Review and modify, if appropriate, the enabled settings from the eTouch.ini master configuration file
  • Open "IIS Manager" and expand to RESC3DEV \ Web Sites
  • Select Default Web Site and right-click/choose New | Virtual Directory...
    • Alias: eTouchWebServices
    • Path: c:\Inetpub\wwwroot\eTouchWebServices
    • Permissions: Read, Run Scripts
  • Select "Properties" on the new virtual directory and ensure:
    • In the "ASP.NET" tab, set the ASP.NET version to 2.0 or greater
    • In the "Directory Security" tab, within the "Authentication and Access Control" group box, click the "Edit..." button and ensure that "Integrated Windows authentication" is checked/enabled
  • Test the web service by attempting to run the "ping" and "pingDatabase" web services. Note that these must be tested via a local URL since, for security purposes, the Web Service test page is only available through local requests. Sample URL to the retrieval service: http://localhost/eTouchWebServices/eTouchSurveyRetrievalService.asmx

Print Service Deployment

  • Ensure the "Print Spooler" service is running and configured to automatically start with Windows
  • Attach the ED printer (Start | Printers and Faxes | Add a Printer | Network Printer | Find in directory | Name = ERXX29)
  • If appropriate, generate a test page by clicking the "Print Test Page" button from the Printer properites dialog.

Production Environment(s)

Overview

  • Web Services
    • Server - ServerL1? -P-CH-W-WWW04
    • Server - ServerL1? -P-CH-W-WWW05
    • Server - ServerL1? -P-CH-W-WWW01 (disaster recovery production)
    • Directory - \\l1-p-ch-w-www04\e$\Inetpub\wwwroot\eTouchWebServices
  • Client

Put setup files here for IS Desktop Engineering to use in creating an SMS scripted installation: file://columbuschildrens.net/isapps/Programs2/Temp/ResearcheTouch2.5

  • Deployment Steps

Web Service Deployment

  • Deploy codebase to eTouchWebServices folder beneath webroot ( e:\Inetpub\wwwroot\eTouchWebServices for prod)
  • Open "IIS Manager" and expand to (Server name) \ Web Sites
  • Select Default Web Site and right-click/choose New | Virtual Directory...
    • Alias: eTouchWebServices
    • Path: e:\Inetpub\wwwroot\eTouchWebServices
    • Permissions: Read, Run Scripts
  • Select "Properties" on the new virtual directory and ensure:
    • In the "ASP.NET" tab, set the ASP.NET version to 2.0 or greater
    • In the "Directory Security" tab, within the "Authentication and Access Control" group box, click the "Edit..." button and ensure that "Integrated Windows authentication" is checked/enabled
  • Test the web service by attempting to run the "ping" and "pingDatabase" web services. Note that these must be tested via a local URL since, for security purposes, the Web Service test page is only available through local requests. Sample URL to the retrieval service: http://localhost/eTouchWebServices/eTouchSurveyRetrievalService.asmx

Print Service Deployment

  • Ensure the "Print Spooler" service is running and configured to automatically start with Windows
  • Attach the ED printer (Start | Printers and Faxes | Add a Printer | Network Printer | Find in directory | Name = ERXX29)
  • If appropriate, generate a test page by clicking the "Print Test Page" button from the Printer properites dialog.

Environment Purpose URL/Location Server(s) Database(s) Current Version Other Information
Production The primary/production environment used by customers/users https://intranet.columbuschildrens.net/webapplications/etouch2EmerDept/        
Development The isolated environment, possibly changing and temporarily unstable, where development activities occur          
Automated Testing An environment refreshed with test data and where scripted testing occurs          
User Acceptance Testing An environment used by testers and/or end-users to validate proper function of a release candidate          
Demonstration A stable environment with sample data, possibly refreshed frequently, for use in demonstrating the product          
Staging/Upgrade An environment where deployment/upgrade activities are rehearsed in preparation for a production deployment          
Training A stable environment where training activities occur; data is often refreshed to a consistent state periodically          

Monitoring Points

This section contains an overview of the critical "points of failure" and associated automated monitoring, if any.

Currently Monitored

  • ED Kiosks
    • Basic host-level availability (host running; networking running; monitoring agent running; reachability through network)
    • Host CPU, disk, memory within tolerances
    • Health eTouch client software running
  • Print Service
    • Basic host-level availability (host running; networking running; monitoring agent running; reachability through network)
    • Host CPU, disk, memory within tolerances
    • "Batch and Print" service/process running
    • Number of files in the pickup directories (metric only; no alerting)
    • Age of oldest file in pickup directories (alerting if over 5 minutes old)
  • ED Printer
    • Basic availability (running; networking running; SNMP running; reachability through network)
    • Pages printed (metric only; no alerting)
    • Status (alerting if not "running")
    • Status Panel display (alert if "Load Paper" displayed)
  • HeT Web Services
    • Exceptions are emailed to Research Informatics Core group

Build/Deployment/Installation Instructions

This section contains instructions and/or notes describing how to build, deploy or otherwise install the application.

Access Provisioning Instructions

This section details the steps needed to grant a user access to the application.

Known Issues

Printing
Files put into this directory on resricfs01 will print to the ED printer:
C:\monitoring-printing\print-dir-het-ed-prod

After successful printing, they are moved here:
C:\monitoring-printing\het-ed-prod-printed

If someone requests a report to be reprinted, simply login to resricfs01 and copy the file from C:\monitoring-printing\het-ed-prod-printed to \\Resricfs01\print-dir-het-ed-prod

ED Printer: file://nchvprt06/ERxx29

Generating Reports

If the report storage and printing server (currently resricfs01) goes down, a report will need to be generated before it can be printed. Regenerate the reports by calling the web service in NetBeans? IDE or another SOAP client using the HOSPITAL\HealtheTouch credentials:

Web service: https://intranet.columbuschildrens.net/etouchwebservices/etouchsurveyresponseservice.asmx?wsdl
Method: CreateReportFile?
Parameters:
formId: 4
resultFormId: [obtain this from the error message email, or a SQL query]

Kiosk users (caregivers) do not see an error message if the report file cannot be created. Research assistants and the social worker are still notified of the positive screening (and the patient name) by pager. They would then look for a printed report and not find one. I think the research assistants need all printed reports for their records, but this isn't an urgent issue.

Miscellaneous Notes / Scratchpad

  • To start/stop the print service remotely:
Topic revision: r16 - 11 Aug 2011 - 22:03:18 - AndyFox
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback