1 / 27

SoftPath: Patch to Success Without Stress

SoftPath: Patch to Success Without Stress. Joan Brueckner Kayla Philhower. Goal:. Create a standard process which explains each step and all expectations of a SoftPath Patch Project To make your life easier. What is the Patch Process?. Patch Complete!. PTCH Env is Created.

dunneback
Télécharger la présentation

SoftPath: Patch to Success Without Stress

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SoftPath: Patch to Success Without Stress Joan Brueckner Kayla Philhower

  2. Goal: • Create a standard process which explains each step and all expectations of a SoftPath Patch Project • To make your life easier

  3. What is the Patch Process? Patch Complete! PTCH Env is Created Kick-Off Call Monitor for 1 Week Go-Live Readiness Go-Live Client Validates PTCH Env TSS Validates TEST Env TSS Validates PTCH Env

  4. PTCH Environment is Created • New PTCH software is installed • Setups are copied from Production environment

  5. TSS Validates PTCH Environment • Support PCs must be made available for TSS testing • TSS begins validation of PTCH environment • Any issues that are found are resolved prior to client involvement

  6. Kick-Off Call • SCC team and client discuss expectations of the Patch project • Introduces the client to the TSS team • Clarifies client’s needs for the TSS before the client begins validation • Client receives validation checklist from the CRM

  7. TSS Provides Support During Client Validation • Conference calls are scheduled regularly to discuss issues or questions • Client enters tasks for any PTCH validation issues • All task descriptions should start with “PTCH”

  8. Client Testing Tips • Create, process, result at least 2 cases for each case type (S, M, G, A) • Basic and complex workflow – “try to break it” • Document MRNs/case numbers • Have multiple users from different areas of pathology test the env. • Transcriptionists, histotechs, etc.

  9. Client Testing Tips • Confirm IPs or DNS for all printers • Print cassettes, labels, reports for test cases • Run report launcher reports and ODBC/SoftReports • Generally: test workflow first* * time constraints

  10. Go-Live Readiness Meeting • CRM will answer client questions regarding the go-live process • Go-live cannot proceed without completed Client Validation Checklist! • Submit checklist NO LATER than 2 weeks before go-live • Client provides test patient MRNs to TSS for testing

  11. Client PTCH Validation has Stalled… • If client has not validated for more than 90 days, the setups may need to be synched from LIVE to PTCH environment again • This means the client will need to start the validation process all over again

  12. Go-Live: Know Your Schedule • After Hours Go-Live • All tasks have urgency level: Emergency • Task description must start with: GO LIVE ISSUE • Dedicated SCC staff are on-call at time of Go-Live for any/all issues

  13. Go-Live: Know Your Schedule • Business Hours Go-Live • All tasks have urgency level: Emergency • Task description must start with: GO LIVE ISSUE • In-house SCC staff are available as tasks are created

  14. Post Go-Live • Dedicated Patch team works on go-live issues for one week after go-live (or until stable ) • Afterwards, support tasks are distributed to SoftPath TSSs as available

  15. TEST Environment Validation • 3-4 weeks after go-live, the new softwareis synched from Production environment to TEST environment • TSS resolves any issues in support tasks • After validation, TEST and Production environments should match

  16. Types of Patch Projects • Synching Patch Software from PTCH to Production LIVE 4.4.0.1 LIVE 4.4.2.0 (production) PTCH 4.4.2.0 TEST 4.4.0.1 TEST 4.4.2.0 Software ONLY

  17. Types of Patch Projects • Patch Environment becomesthe Production Environment TEST 4.4.0.1 LIVE 4.4.0.1 (production) “OFF” LIVE3 4.4.2.0 (production) TEST3 4.4.2.0 LIVE3 4.4.2.0 “ON”

  18. PTCH Environment Becomes the Production Environment • ALL setup changes made in current Production Environment MUST be made in PTCH Environment • If the client does not maintain their PTCH environment with the same setup changes as Production, there could be issues at Go-Live that affect patients • SETUPS WILL NOT BE SYNCHED AT GO-LIVE

  19. Future Delivery & Safety Bins • TSS will follow up with client to review all tasks suspended to Future Delivery Bin and Safety Bin • TSS confirms that all issues scheduled for correction in the new environment are resolved

  20. Release Note Query

  21. Release Note Query

  22. Release Note Query

  23. Release Note Query

  24. Release Note Query • Important to compare current version to new version • Test for enhancements and corrections • Release Note Query displays corrections/enhancements in each higher version

  25. Thank you! Questions?

More Related