Healthcaresys8

Component8:InstallationandMaintenanceofHealthITSystemsInstructorManualVersion3.
0/Spring2012HealthITWorkforceCurriculumInstallationandMaintenanceof2HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
NotestoInstructorsThisInstructorManualisaresourceforinstructorsusingthiscomponent.
Eachcomponentisbrokendownintounits,whichincludethefollowingelements:LearningobjectivesSuggestedstudentreadings,texts,referencelinkstosupple-mentthenarratedPowerPointslidesLectures(voiceoverPowerPointinFlashformat);PowerPointslides(MicrosoftPowerPointformat),lecturetranscripts(Mic-rosoftWordformat);andaudiofiles(MP3format)foreachlectureSelf-assessmentquestionsreflectingUnitObjectiveswithanswerkeysand/orexpectedoutcomesApplicationActivities(e.
g.
,discussionquestions,assign-ments,projects)withinstructorguidelines,answerkeysand/orexpectedoutcomesLabs/SimulationsforvirtualmachinesHealthITWorkforceCurriculumInstallationandMaintenanceof3HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
ContentsNotestoInstructors.
2Disclaimer.
9Component8/Unit1.
10Component8/Unit2.
14Component8/Unit3.
17Component8/Unit4.
19Component8/Unit5.
22Component8/Unit6.
24Component8/Unit7.
27Component8/Unit8.
29Component8/Unit9.
32Component8/Unit10.
36Component8/Unit11.
39ComponentAcronymGlossary.
42CreativeCommonsAttribution-NonCommercial-ShareAlike3.
0Unported52Appendix1:SunnyHappyCareFamilyPracticeScenario.
53HealthITWorkforceCurriculumInstallationandMaintenanceof4HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
ComponentOverviewThiscomponentcoversfundamentalsofselection,installationandmain-tenanceoftypicalElectronicHealthRecords(EHR)systems.
Studentswillbeintroducedtotheprinciplesunderlyingsystemconfigurationincludingbasichardwareandsoftwarecomponents,principlesofsystemselection,planning,testing,troubleshooting,andfinaldeployment.
Systemsecurityandprocedureswillalsobeintroducedinthiscomponent.
EachLearningUnitrequires2-5contact/instructionalhoursandanaddi-tional6-15hoursofindependentorteamworkonthepartofthestudentinordertobecompletedsuccessfully.
Eachunitcontainsmorematerialthanwouldlikelybeusedinanyoneteaching/learningexperiencesothattheinstructorcanpickandchoosematerialmostapplicabletolocalworkforceneeds.
Unit1,ElementsofaTypicalEHRSystemUnit2,SystemSelection–SoftwareandCertificationUnit3,SystemSelection–FunctionalandTechnicalRequirementsUnit4,StructuredSystemsAnalysisandDesignUnit5,SoftwareDevelopmentLifeCycleUnit6,SystemSecurityProceduresandStandardsUnit7,SystemInterfacesandIntegrationUnit8,Troubleshooting;MaintenanceandUpgrades;InteractionwithVendors,Developers,andUsersUnit9,CreatingFaultTolerantSystems,Backups,andDecommissioningUnit10,DevelopingaTestStrategyandTestPlanUnit11,PilotTestingandFullScaleDeploymentThisentireComponentisestimatedtorequire18-45totalcontact/instruc-tionalhoursplus54-135additionalhoursofindependentorteamwork,de-pendingonthelearningactivitiesandassessmentsusedwithineachunit.
ComponentObjectivesAtthecompletionofthiscomponent,thestudentwillbeableto:DescribetheuseofclientandserverhardwareforaccesstoandstorageofEHRsDescribenetworkneedsforaccesstoandstorageofEHRsIdentifytheapplicationsoftwareandback-enddatastoragesoftwareneededforacomprehensive,effectiveHealthITSystemHealthITWorkforceCurriculumInstallationandMaintenanceof5HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
CompareandcontrastCOTS(CommercialOff-The-Shelf)andIn-House/homegrownsystemsanddescribetheirrela-tiveadvantagesanddisadvantagesVerifysystemcompliancewithONC-ATCBcertificationIdentifypurposeandcategoriesofARRA"MeaningfulUse"criteriaIdentify12possiblestepstochoosinganEHRsystemGatherfunctionalrequirementsfrominstitutionandusersDocumentuse-casesandrelatethemtofunctionalrequire-mentsIdentifythe8basiccomponentstoaprojectplanDefinetheroleofaprojectmanagerEquatethebasicprojectplancomponentstoatypicalEHRimplementationplanCreateaprojectplanforsystemdesignandimplementationDefinethestepsoftheSoftwareDevelopmentLifeCycle(SDLC)andthepurposeandimportanceofeach.
DescribedifferentmodelsoftheSDLCandtheirkeydiffer-ences.
DescribehowandwhyanHITsoftwareapplicationwouldgothroughtheSDLCIdentifyregulatoryrequirementsforEHRSandintegrateintotheprojectplanIdentifybestpracticesforOSandnetworksystemsecurityinstallationandpatches(suchasthoseprovidedbyvendors,SANs,andISC2)andintegrateintoprojectplanIdentifyandassessprotectionmeasuresincludingaccesscontrol,firewalls,intrusiondetectionandencryptionProvidetrainingforsystemusersregardingthemethodsandimportanceofsecuritycomplianceDetermineanddocumentsysteminterfacesandintegrationrequirementsDescribethepitfallsassociatedwithinstallinganewapplica-tioninanenvironmentofpre-existingapplicationsGiveexamplesofinterfacingmodalitiesIdentifyandimplementaneffectivetroubleshootingproce-dureforreporting,evaluating,fixing,deploying,andfollow-upoferrors,problems,orlimitationsforthesystemIntegratedowntimescheduleforOS,network,database,andclientapplicationmaintenanceandupdatesHealthITWorkforceCurriculumInstallationandMaintenanceof6HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Developaprocessforcommunicatingrequirementsandsup-plyingupdatesbetweenvendors/developerandusersCreateabaselineforsystemperformancemeasurementandcomparisonfortroubleshootingCreateredundancyandfault-toleranceinsystemsforaccessanddatastorage,providinghighperformanceandreliabilityBackupandrestoredatabases,applications,andoperatingsystemsDevelopaplanfordecommissioningsystemsanddataGatheruserfeedbackandperformancebaselineforsystemvalidationandtestingDocumentproblemswiththeirresolutionstatusCreate,execute,anddocumentatestplanIdentifypilotgroupandplanscopeofpilotInstallpilotsystem,trainpilotusers,andmakepilotavailableGatherandprioritizefeedbackfrompilottest,revisingprojectplanifnecessaryDevelopandimplementstrategyfor:oCommunicatingdeploymentplantoendusersandman-agementoTechnicalsupportofdeployment(e.
g.
liveon-sitesupportversusphone/Internetsupport)oGettingfeedbackfromendusersfollowingdeploymentoEvaluatingusageandcapacityofsystemresourcesunderconditionsoffulldeploymentDeployrevisedsystemHealthITWorkforceCurriculumInstallationandMaintenanceof7HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
ComponentAuthorsAssignedInstitutionDukeUniversity,Durham,NCTeamLeadsScottNealDurhamTechnicalCommunityCollegeR.
ClaytonMusser,MD,MSDukeUniversityPrimaryContributingAuthorsScottNealDurhamTechnicalCommunityCollegeR.
ClaytonMusser,MD,MSDukeUniversityHarryBulbrookDurhamTechnicalCommunityCollegeLectureNarration/SoundEngineerSoundEngineerRalandTechnologiesLLC1387FairportRoadSuite1050Fairport,NY14450DavidFlass-ProjectManagerHealthITWorkforceCurriculumInstallationandMaintenanceof8HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
TeamMembersScottNealDurhamTechnicalCommunityCollegeInformationSystemsSecurity/NetworkingTechnologiesR.
ClaytonMusser,MD,MSDukeUniversityAssistantProfessor,InternalMedicine&MedicalInformaticsHarryBulbrookDurhamTechnicalCommunityCollegeCoodinator/Instructor,InformationSystemsSecurity/NetworkingTechnologiesHealthITWorkforceCurriculumInstallationandMaintenanceof9HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
DisclaimerThesematerialswerepreparedunderthesponsorshipofanagencyoftheUnitedStatesGovernment.
NeithertheUnitedStatesGovernmentnoranyagencythereof,noranyoftheiremployees,makesanywarranty,expressorimplied,orassumesanylegalliabilityorresponsibilityfortheaccuracy,completeness,orusefulnessofanyinformation,apparatus,product,orprocessdisclosed,orrepresentsthatitsusewouldnotinfringeprivatelyownedrights.
Referencehereintoanyspecificcommercialproduct,pro-cess,orservicebytradename,trademark,manufacturer,orotherwisedoesnotnecessarilyconstituteorimplyitsendorsement,recommenda-tion,orfavoringbytheUnitedStatesGovernmentoranyagencythereof.
TheviewsandopinionsofauthorsexpressedhereindonotnecessarilystateorreflectthoseoftheUnitedStatesGovernmentoranyagencythereof.
Likewise,theabovealsoappliestotheCurriculumDevelopmentCenters(includingColumbiaUniversity,DukeUniversity,JohnsHopkinsUniversity,OregonHealth&ScienceUniversity,UniversityofAlabamaatBirming-ham,andtheiraffiliatedentities).
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof10HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit1UnitTitleElementsofaTypicalEHRSystemUnitDescriptionThisunitprovidesanoverviewofwhatatypicalelectronichealthrecordsystemisandfocusesontheelementsthatmakeupsuchasystem--hardware,networks,software,andstoragerequirements.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
DescribetheuseofclientandserverhardwareforaccesstoandstorageofEHRs2.
DescribenetworkneedsforaccesstoandstorageofEHRs3.
Identifytheapplicationsoftwareandback-enddatastoragesoftwareneededforacomprehensive,effectiveHealthITSystemUnitTopics/LectureTitles1aElementsofaTypicalElectronicHealthRecordSystem1bElementsofaTypicalElectronicHealthRecordSystemUnitReferences(Alllinksaccessibleasof3/12/2012)Lecture1aDesRoches,C.
M.
etal.
(2008).
ElectronicHealthRecordsinAmbulatoryCare—ANationalSurveyofPhysicians.
NEnglJMed.
359:50-6.
http://www.
nejm.
org/doi/full/10.
1056/NEJMsa0802005Dickinson,G.
,Fischetti,L.
,&Heard,S.
(2003).
HL7EHRSystemFunc-tionalModelandStandard.
RetrievedJuly,2010,fromHIMSS.
org:http://www.
himss.
org/Content/Files/EHR_Functional_Model_Ballot.
pdf*Garrett,P.
,&Seidman,J.
(2011,January4).
EMRvsEHR–WhatistheDifferenceHeathITBuzz.
RetrievedDecember,2011,fromhttp://www.
healthit.
gov/buzz-blog/electronic-health-and-medical-records/emr-vs-ehr-difference/Greenhalgh,T.
etal(2009).
"TensionsandParadoxesinElectronicPatientRecordResearch:ASystematicLiteratureReviewUsingtheMeta-Nar-rativeMethod".
[PDFontheInternet].
TheMilbankQuarterly.
[CitedJune2011].
http://www.
milbank.
org/quarterly/8704feat.
html**Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof11HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Gurley,L.
(2004).
Advantagesanddisadvantagesofelectronicmedicalrecords.
Retrievedfromhttp://www.
aameda.
org/MemberServices/Exec/Articles/spg04/Gurley%20article.
pdf*InstituteofMedicine.
(2001,March1).
Crossingthequalitychasm:anewhealthsystemforthe21stCentury.
RetrievedJune30,2010,fromhttp://www.
nap.
edu/catalog/10027.
htmlPawola,L.
(2011,February22).
Thehistoryoftheelectronichealthrecord.
HealthInformaticsandHealthInformationManagement.
RetrievedDe-cember,2011,fromhttp://healthinformatics.
uic.
edu/the-history-of-the-elec-tronic-health-record/*Maons,D.
(2011,November11).
EHRsareinevitable,expertssay.
Heath-careITNews.
Retrievedfromhttp://www.
healthcareitnews.
com/news/ehrs-are-inevitable-experts-sayMedicalAssociates.
ElectronicMedicalRecord.
RetrievedSeptember2011fromhttp://www.
medical-software.
org/electronic-medical-record.
htmlSteele,E.
(2009,December16).
ResearchexplainswhyEHRswon'tachieve"MeaningfulUse.
"RetrievedNov,2011,fromhttp://blog.
srssoft.
com/2009/12/research-explains-why-ehrs-won%e2%80%99t-achieve-%e2%80%9cmeaningful-use%e2%80%9d/*Torrey,T.
WhatisanEMR(ElectronicMedicalRecord)orEHR(ElectronicHealthRecord)"(2011,April11).
RetrievedJune,2011,fromPatients.
About.
Com:http://patients.
about.
com/od/electronicpatientrecords/a/emr.
htmTorrieri,M.
(2011,August23).
EHRadoptiongrowsslowly,steadi-lyatsmallpractices.
Retrievedfromhttp://www.
searchmedica.
com/resource.
htmlrurl=http%3A%2F%2Fwww.
physicianspractice.
com%2Fblog%2Fcontent%2Farticle%2F1462168%2F1933985%3F-CID%3Drss&q=Kleaveland&c=pm&ss=physiciansPractice&p=Convera&-fr=true&ds=0&srid=3Wikipedia.
(2011,August).
ClientServerModel.
RetrievedJune,2011,fromWikipedia.
com.
http://en.
wikipedia.
org/wiki/Client%E2%80%93serverLecture1aCharts,Tables,Figures1.
1Figure:MITRE,2006ElectronicHealthData—PreEHRFigure1ElectronicHealthRecordsOverview,http://www.
ncrr.
nih.
gov/publications/informatics/EHR.
pdf*UsedwithPermission.
1.
2Figure:MITRE,2006EHRConceptOverviewFigure2ElectronicHealthRecordsOverview,http://www.
ncrr.
nih.
gov/publications/informat-ics/EHR.
pdf*Usedwithpermission1.
3Figure:Neal,Scott.
2011.
ClientServerModel.
UsedwithPermission*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof12HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Lecture1aImagesNoneusedinthislecture.
Lecture1b1.
Kleaveland,B.
EHRImplementation:Whatyouneedtoknowtohaveasuccessfulproject:Part2.
PhysiciansPractice.
Retrievedfromhttp://www.
physicianspractice.
com/files/audioconference/pdfs/id_7.
pdfCFID=1675309&CFTOKEN=75588070*2.
Torrey,T.
(2011,April11).
WhatisanEMR(ElectronicMedicalRecord)orEHR(ElectronicHealthRecord)RetrievedJune,2011,frompatients.
about.
com:http://patients.
about.
com/od/electronicpatientrecords/a/emr.
htm.
3.
Torrieri,Marisa(2011,August23).
EHRAdoptionGrowsSlowly,SteadilyatSmallPractices.
http://www.
searchmedica.
com/search.
htmlq=Torrieri4.
Wikipedia.
(2008,July).
ThinClient.
RetrievedfromWikipedia.
com:http://en.
wikipedia.
org/wiki/Thin_client.
5.
Wikipedia.
Computernetwork.
RetrievedfromWikipedia.
com:http://en.
wikipedia.
org/wiki/Computer_network.
Lecture1bCharts,Tables,Figures1.
1Table:Neal,Scott.
EHRHardware–Servers.
Usedwithpermission.
Lecture1bImagesSlide15:Laptop.
CourtesyScottNeal.
Usedwithpermission.
Slide19:LocalAreaNetwork(LAN).
CourtesyScottNeal.
Usedwithper-mission.
Slide20:WideAreaNetwork(WAN).
CourtesyScottNeal.
Usedwithpermission.
UnitRequiredReadings.
Noneforthisunit.
UnitSuggestedReadings1.
"What'sInsideMyComputer"byJonathanStrickland,November2006,http://www.
howstuffworks.
com/inside-computer.
htmThis"HowStuffWorks"articleandvideoexplainsthesevenmajorcomponentsinsideatypicalcomputersystem.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof13HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
2.
"UnderstandingApplicationServers"byAjaySrivastava&AnantBhargava2003http://hosteddocs.
ittoolbox.
com/AS030504.
pdfThisarticleexplainsindepthhowapplicationserverswork,particularlyinathreetieredsystemsimilartoatypicalEHRsystemstructure.
3.
"WhatisaServer"byWebopedia,http://www.
webopedia.
com/DidYouKnow/Hardware_Software/2005/servers.
aspAshortbutthorougharticleaboutthefunctionofaserver,typesofservers,andhowthetermappliestohardwareandsoftware.
StudentApplicationActivitiescomp8_unit1_activity.
doccomp8_unit1_activity_key.
doccomp8_unit1_self_assess.
doccomp8_unit1_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof14HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit2UnitTitleSystemSelection–SoftwareandCertificationUnitDescriptionThisunitwilldiscussthedifferencesinCOTS(CommercialOff-The-Shelf)andin-house/homegrownsystemsandhowtoselectthesystemtomeettheneedsoftheendusers.
Wewillalsolookattheadvantagesofpur-chasingaCCHIT-certifiedsystemanddiscussARRAand"meaningfuluse"inthecontextofEHRsystems.
LastlywewilllookatestimatingthetypicalcostsassociatedwithEHRsystemstartup.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
CompareandcontrastCOTS(CommercialOff-The-Shelf)andin-house/homegrownsystemsanddescribetheirrelativeadvantagesanddisadvantages.
2.
VerifysystemcompliancewithONC-ATCBcertification.
3.
IdentifypurposeandcategoriesofARRA"MeaningfulUse"criteria.
UnitTopics/LectureTitles2SystemSelection–SoftwareandCertificationUnitReferences(Alllinksaccessibleasof3/12/2012)Lecture21.
AboutARRA.
RetrievedfromHITECHAnswerswebsite:http://www.
hitechanswers.
net/about/about-arra/2.
ARRAMeaningfulUseSnapshot.
(n.
d.
).
RetrievedfromMedicalInformationTechnology,Inc.
website:http://www.
meditech.
com/in-teroperability/pages/ARRA_snapshot_final_0311.
pdf3.
CertifiedHealthITProductList.
RetrievedfromOfficeoftheNation-alCoordinatorforHealthInformationTechnology,USDepartmentofHealth&HumanServiceswebsite:http://onc-chpl.
force.
com/ehrcert4.
ElectronicMedicalRecord.
RetrievedJune20,2010,from:http://en.
wikipedia.
org/wiki/Meaningful_Use#Meaningful_Use*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof15HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
5.
EHRIncentiveProgramsOverview.
(n.
d.
).
RetrievedfromCentersforMedicare&MedicaidServiceswebsite:https://www.
cms.
gov/EHRIncentivePrograms/6.
MedicareandMedicaidPrograms;ElectronicHealthRecordIncen-tiveProgram(2010,July).
FederalRegister.
[Internet].
Retrievedfromhttp://www.
federalregister.
gov/articles/2010/07/28/2010-17207/medicare-and-medicaid-programs-electronic-health-record-incen-tive-program.
7.
Fornes,D.
(2008,February6).
ShouldCCHITInfluenceYourEHRSelection[Weblogpost].
RetrievedfromSoftwareAdvice-TheMedicalBlog:http://blog.
softwareadvice.
com/articles/medical/should-cchit-influence-your-ehr-selection8.
Gates,M.
(2009,Winter).
AllSystemsGoHowtoSelectanEHRThatMeetsYourNeeds.
CorrectCare,Retrievedfromhttp://www.
ncchc.
org/pubs/CC/selecting_ehr.
html*9.
GoalsforEHRSystem.
RetrievedJune20,2010,fromHealthTech-nologyReviewwebsite:http://www.
healthtechnologyreview.
com/viewarticle.
phpaid=11310.
HITECHActEnforcementInterimFinalRule.
(n.
d.
).
RetrievedfromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/administrative/enforcementrule/hitechen-forcementifr.
html11.
McKinney,D.
(2001,August).
ImpactofCommercialOff-The-Shelf(COTS)SoftwareandTechnologyonSystemsEngineering.
Re-trievedfromPresentationtoINCOSEChapterswebsite:http://www.
incose.
org/northstar/2001Slides/McKinney%20Charts.
pdf12.
MedicareandMedicaidPrograms;ElectronicHealthRecordIn-centiveProgram;FinalRule,75Fed.
Reg.
44314(2010)42CFRParts412,413,422,and495http://edocket.
access.
gpo.
gov/2010/pdf/2010-17207.
pdf13.
ONC-AuthorizedTestingandCertificationBodies.
RetrievedfromOfficeoftheNationalCoordinatorforHealthInformationTechnol-ogy,USDepartmentofHealth&HumanServiceswebsite:http://healthIT.
hhs.
gov/ATCBs*14.
Pizzi,R.
(2007,October30).
EHRadoptionan"uglyprocess,"butCCHITcanimproveappeal.
RetrievedfromHealthcareITNewswebsite::http://www.
healthcareitnews.
com/news/ehr-adoption-ug-ly-process-cchit-can-improve-appeal*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof16HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
15.
Rice,R.
(2009).
TestingCOTS-BasedApplications.
RetrievedJune21,2010,fromhttp://www.
riceconsulting.
com/articles/test-ing-COTS-based-applications.
htm16.
Standards&Certification.
RetrievedfromOfficeoftheNationalCoordinatorforHealthInformationTechnology,USDepartmentofHealth&HumanServiceswebsite:http://healthit.
hhs.
gov/portal/server.
pt/community/healthit_hhs_gov__standards_and_certifica-tion/1153*17.
Standards&CertificationCriteriaFinalRule.
RetrievedfromOfficeoftheNationalCoordinatorforHealthInformationTechnology,USDepartmentofHealth&HumanServiceswebsite:http://healthit.
hhs.
gov/portal/server.
pt/community/healthit_hhs_gov__standards_ifr/1195*Lecture2Charts,TablesandFiguresNoneusedinthislecture.
Lecture2ImagesSlide13:ARRArecovery.
govlogohttp://www.
recovery.
gov/News/mediakit/Picture%20Library/circle_recovery_logo.
jpg*Slide13:CenterforMedicareandMedicaidServicesEHRIncentivePro-gramslogohttp://www.
cms.
gov/EHRIncentivePrograms/Downloads/EH-RIncentiveLogoweb.
JPGUnitRequiredReadingsNoneforthisunit.
UnitSuggestedReadings1.
ShouldCCHITInfluenceYourEHRSelectionByDonForneshttp://www.
softwareadvice.
com/articles/medical/should-cchit-influ-ence-your-ehr-selection/.
AnexcellentoverviewofCCHIT'sroleinEHRselectionandthecriteriacertifiedbytheorganization.
2.
HealthcareIndustryshowdemonstrateswealthofopportunities,BySteveHickshttp://mindset.
mercurypay.
com/p=475*.
AnoverviewofInteroperability,MeaningfulUse,andRevenueCycleManage-mentStudentApplicationActivitiescomp8_unit2_actvities.
doccomp8_unit2_activity_key.
doccomp8_unit2_self_assess.
doccomp8_unit2_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof17HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit3UnitTitleSystemSelection–FunctionalandTechnicalRequirementsUnitDescriptionThisunitwilldiscussthe12differentstepsassociatedwithsystemselectionfocusingondefininguserfunctionalrequirementsofsystemsandtechnicalrequirements(bythesystem),includinghowtothedetermine,document,prioritize,andactonthoserequirementsthroughtheuseofcasestudiesandothermeans.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Identify12possiblestepstochoosinganEHRsystem2.
Gatherfunctionalrequirementsfrominstitutionandusers3.
Documentuse-casesandrelatethemtofunctionalrequirementsUnitTopics/LectureTitles3SystemSelection–FunctionalandTechnicalRequirementsUnitReferences(Alllinksaccessibleas1/26/2012)Lecture31.
Adler,K.
G.
(2005).
Howtoselectanelectronichealthrecordsys-tem.
FamPractManag,12(2),55-62.
Retrievedfromhttp://www.
aafp.
org/fpm/2005/0200/p55.
html.
2.
HIMSS.
(2011).
DaviesAwardpastrecipients(forachievementinimplementationofEHRs).
Retrievedfromhimss.
org:http://www.
himss.
org/davies/pastRecipients_org.
asp.
3.
HL7ElectronicHealthRecord(EHR)WorkGroup.
(2007).
HL72007EHR-SFunctionalModel.
Retrievedfromhttp://www.
hl7.
org/ehr/downloads/index_2007.
asp.
4.
IllinoisFoundationforQualityHealthCare.
GuidelinesforEvaluat-ingEHRs.
(2009).
Retrievedfromhttp://www.
ifmc-il.
org/provider/documents/guidelines_for_evaluating_ehrs.
pdf*.
5.
Johnson,N.
(2011,September12).
HHSlauncheshealthIT.
gov,FederalTimes.
com.
Retrievedfromhttp://blogs.
federaltimes.
com/federal-times-blog/2011/09/12/hhs-launches-healthit-gov/*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof18HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
6.
OfficeoftheNationalCoordinator(ONC)forHealthInformationTechnology.
HowtoImplementEHRs,Step3:SelectorUpgradetoaCertifiedEHR.
Retrievedfromhttp://www.
healthit.
gov/provid-ers-professionals/step-3-select-or-upgrade-certified-ehr.
*7.
Quinsey,C.
A.
(2006).
UsingHL7standardstoevaluateanEHR.
JournalofAHIMA,77(4),64A-64C.
Retrievedfromhttp://library.
ahima.
org/xpedio/groups/public/documents/ahima/bok1_031102.
hcspdDocName=bok1_031102*.
8.
StratisHealth.
(2009).
RequirementsAnalysis.
Retrievedfromhttp://www.
stratishealth.
org/documents/HITToolkitNH/1.
Adopt/1.
3Select/1.
3.
5Requirements_Analysis.
doc.
Lecture3Charts,Tables,Figures3.
1Table:Quinsey,C.
A.
(2006).
UsingHL7standardstoevaluateanEHR.
JournalofAHIMA,77(4),64A-64C.
Retrievedfromhttp://library.
ahima.
org/xpedio/groups/public/documents/ahima/bok1_031102.
hcspd-DocName=bok1_031102*.
Lecture3ImagesNoneinthislecture.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
ShouldCCHITInfluenceYourEHRSelectionByDonForneshttp://www.
softwareadvice.
com/articles/medical/should-cchit-influ-ence-your-ehr-selection/AnexcellentoverviewofCCHIT'sroleinEHRselectionandthecriteriacertifiedbytheorganization.
2.
HealthcareIndustryshowdemonstrateswealthofopportunities,BySteveHickshttp://mindset.
mercurypay.
com/p=475*AnoverviewofInteroperability,MeaningfulUse,andRevenueCycleManage-mentStudentApplicationActivitiescomp8_unit3_actvities.
doccomp8_unit3_activity_key.
doccomp8_unit3_self_assess.
doccomp8_unit3_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof19HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit4UnitTitleStructuredSystemsAnalysisandDesignUnitDescriptionThisunitwilldiscussthebasicsofdevelopingaprojectplanandtheroleofaprojectmanager.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Identifythe8basiccomponentstoaprojectplan2.
Definetheroleofaprojectmanager3.
EquatethebasicprojectplancomponentstoatypicalEHRimple-mentationplan4.
CreateaprojectplanforsystemdesignandimplementationUnitTopics/LectureTitles4StructuredSystemsAnalysisandDesignUnitReferences(Alllinksaccessibleasof2/15/2012)Lecture4Brown,C(2009,March).
"ItUsedtobetheIronTriangle"[Internet].
Availablefromhttp://www.
betterprojects.
net/2009/03/it-used-to-be-iron-triangle.
htmlColumbus,Suzanne.
"SmallPractice,BigDecision:SelectinganEHRSystemforSmallPhysicianPractices.
"JournalofAHIMA77,no.
5(May2006):42-46.
AvailableontheInternet:http://library.
ahima.
org/xpedio/groups/public/documents/ahima/bok1_031357.
hcspdDocName=bok1_031357DerGurahian,Jean(2010,March).
"Slow,steadyEHRimple-mentationplanbetterfordoctors'offices"[Internet].
Availablefrom:http://searchhealthit.
techtarget.
com/news/2240016960/Slow-steady-EHR-implementation-plan-better-for-doctors-officesHohly,Marge.
ProjectPlanDefinition[Internet].
2007.
[CitedJuly2010]:[about5screens].
http://www.
cerritos.
edu/hohly/WorkExperi-ence/projectplan_instructions.
htmLauni,Joe.
CreatingaProjectPlan.
JNM[serialontheInternet].
1999Sept;[cited2010August15]http://www.
tdan.
com/view-arti-cles/5266*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof20HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Lonergan,Kevin.
ProjectManagement.
FreeManagementLibrary[Internet];[cited2010August5];Availablefrom:http://www.
man-agementhelp.
org/plan_dec/project/project.
htmARoadmapforanEHRImplementationataPractice.
BinarySpectrum[Internet].
http://www.
binaryspectrum.
com/HealthcareS-olutions/ElectronicMedicalRecords/Roadmap-forimplementa-tion-of-EHRsystem-at-a-practice.
htmlTurbit,Neville(2005,June).
"DefiningtheScopeofaProject"[Inter-net].
PerfectProject.
com.
AvailableFrom:http://www.
projectperfect.
com.
au/info_define_the_scope.
php.
Wikipedia(2011,December).
"Scope(ProjectManagement)"[Inter-net].
CitedDecember2011fromWikipedia.
com:http://en.
wikipedia.
org/wiki/Scope_(project_management*.
Wikipedia(2010,December).
"Scope(ProjectManagement)"[Inter-net].
CitedDecember2010fromWikipedia.
com:http://en.
wikipedia.
org/wiki/Scope_(project_management*Lecture4Charts,Tables,FiguresNoneusedinthislecture.
Lecture4ImagesSlide5:TheProjectDiamond.
CourtesyScottNeal.
Usedwithpermission.
Slide7:TheRoleofaProjectManager.
CourtesyScottNeal.
Usedwithpermission.
UnitRequiredReadingsNoneusedinthislecture.
UnitSuggestedReadings1.
"HowtoSuccessfullyNavigateYourEHRImplementation"byKen-nethAdler,February2007,http://www.
aafp.
org/fpm/2007/0200/p33.
html2.
"EHRImplementationRoadmap:2005Pilot"2005http://hosted-docs.
ittoolbox.
com/AS030504.
pdf.
ThisisanEHRImplementationplantemplatestudentsmayuseasaguidetodevelopingtheirownplansfortheactivities.
StudentApplicationActivitiescomp8_unit4_activity.
doccomp8_unit4_activity_key.
doccomp8_unit4_self_assess.
doccomp8_unit4_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof21HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit5UnitTitleSoftwareDevelopmentLifeCycleUnitDescriptionThisunitintroducesthestudenttotheSDLCmodelandexploresitsappli-cationtowell-knownsoftwareanditsutilityforhealthcareITsystems.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
DefinethestepsoftheSoftwareDevelopmentLifeCycle,orSDLC,andthepurposeandimportanceofeach.
2.
DescribedifferentmodelsoftheSDLCandtheirkeydifferences.
3.
DescribehowandwhyanHITsoftwareapplicationwouldgothroughtheSDLC.
UnitTopics/LectureTitles5SoftwareDevelopmentLifeCycleUnitReferences(Alllinksaccessibleasof1/26/2012)Lecture51.
Kay,R.
I.
(2002,May14).
QuickStudy:SystemDevelopmentLifeCycle.
ComputerWorld.
com.
,Retrievedfromhttp://www.
computer-world.
com/s/article/71151/System_Development_Life_Cycletaxon-omyId=0112.
Sofandi,A.
(2010,August31).
IntroductiontoSoftwareDevel-opmentLifeCycle(SDLC).
RetrievedfromAlphaSoftIndonesiawebsite:http://agusofyandi.
wordpress.
com/2010/08/31/introduc-tion-to-software-development-life-cycle-sdlc/Lecture1bCharts,Tables,FiguresNoneinthislecture.
Lecture1bImagesSlide6:WaterfallmodelofSDLC.
ImagecourtesyofScottNeal.
Slide7:IterativemodelofSDLC.
ImagecourtesyofScottNeal.
Slide20:WaterfallmodelofSDLC.
ImagecourtesyofScottNeal.
Slide23:IterativemodelofSDLC.
ImagecourtesyofScottNeal.
Slide24:SpiralmodelofSDLC.
ImagecourtesyofScottNeal.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof22HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
SoftwaredevelopmentLifeCycle"VolumesIandIIbytheStateofMaryland,RevisedAugust2008,http://doit.
maryland.
gov/policies/Documents/sdlc/sdlcvol1.
pdf*andhttp://doit.
maryland.
gov/policies/Documents/sdlc/sdlcvol2.
pdf*ThesearticlesgiveagreatindepthintroductiontomanaginglargescaleprojectsusingSDLC.
ThesearticlesserveastheStateofMaryland'sguidelinesforSDLCwithstep-by–stepbreakdownsofeachoftheacceptedSDLCphases.
2.
SystemsdevelopmentLifeCycleModels.
"[PowerpointviatheIn-ternet].
http://www.
docstoc.
com/docs/7806897/SDLC-ModelsThisisaconciseintroductiontoawidevarietyofSDLCmodelsincludingthosediscussedinthelecture.
3.
IntroductiontoSoftwaredevelopmentLifeCycle"asfoundinAgusSoyfandi'sbloghttp://agusofyandi.
wordpress.
com/2010/08/31/introduction-to-software-development-life-cycle-sdlc/ThisarticleoffersamoreabridgedperspectivetoSDLCandSDLCmethodolo-gies.
4.
QuickStudy:SystemsDevelopmentLifeCycle.
"ByRusselKay(alsoavailableinpodcastfromthewebsite.
)http://www.
computer-world.
com/s/article/71151/System_Development_Life_Cycletaxon-omyId=011AnotherintroductiontoSDLC,thewaterfallmodel,andthespiralmodel.
Thenexttext,whichmaybebehinda"paywall"ornoteasilyaccessible,sinceitissuggested.
StudentApplicationActivitiescomp8_unit5_activity.
doccomp8_unit5_activity_key.
doccomp8_unit5_self_assess.
doccomp8_unit5_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof23HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit6UnitTitleSystemSecurityProceduresandStandardsUnitDescriptionThisunitincludesFederalStateandlocalhealthinformationregulationsforEHRs,computerandnetworksystemvulnerabilitiesandbestpracticesforidentificationandmitigationofthosevulnerabilities,informationaccessandprotectionmeasures,andusersecuritytraining.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
IdentifyregulatoryrequirementsforEHRs2.
Providetrainingforsystemusersregardingthemethodsandimportanceofsecuritycompliance3.
Identifyadministrative,physical,andtechnicalsafeguardsforsystemsecurityandregulatorycompliance4.
Identifybestpracticesforsystemsecurity5.
Identifybestpracticesforrisk/contingencymanagementUnitTopics/LectureTitles6SystemSecurityProceduresandStandardsUnitReferences(Alllinksaccessibleasof1/31/2012)Lecture6a1.
DepartmentofHealthandHumanServices(HHS),OfficeofCivilRights(OCR),HIPAAPrivacyRule.
45CFRSubtitleA(10-1-11Edition)Part154.
514RetrievedJanuary20,2012fromGPO:http://www.
gpo.
gov/fdsys/pkg/CFR-2011-title45-vol1/pdf/CFR-2011-ti-tle45-vol1-sec164-514.
pdf2.
EnforcementHighlights.
(2012,January12)RetrievedfromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/enforcement/highlights/index.
html3.
Hamilton,K.
(2009,January15).
EHRsecurityandprivacy.
Re-trievedfromSCMagazinewebsite:http://www.
scmagazine.
com/ehr-security-and-privacy/article/125983/*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof24HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
4.
MinnesotaHealthInformationClearinghouse,MedicalRecordsInformation.
(n.
d.
)RetrievedJanuary12,2012fromMinnesotaDepartmentofHealth:http://www.
health.
state.
mn.
us/clearinghouse/medrecords.
html5.
NumbersataGlance.
(n.
d.
)RetrievedJanuary12,2012,fromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/enforcement/highlights/indexnumbers.
html6.
Poremba,S.
M.
(2008,May23).
RetrievedfromSCMagazinewebsite:http://www.
scmagazine.
com/proliferating-hipaa-com-plaints-and-medical-record-breaches/article/110555/7.
SummaryoftheHIPAAPrivacyRule.
(n.
d.
).
RetrievedfromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/understanding/summary/index.
html8.
SummaryoftheHIPAASecurityRule.
(n.
d.
).
RetrievedfromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/understanding/srsummary.
htmlLecture6aCharts,Tables,FiguresNoneinthislecture.
Lecture6aImagesNoneinthislecture.
Lecture6b1.
CommonTypesofNetworkAttacks.
(n.
d.
)MicrosoftWindowsTCP/IPCoreNetworkingGuide.
DistributedSystemsGuide,Windows2000Server.
http://technet.
microsoft.
com/en-us/library/cc959354.
aspx2.
Hartley,Carolyn(2005).
ASecureEHRFoundation.
[PowerPointslides].
Retrievedfromhttp://www.
mtech.
edu/nchci/EHRConfer-ence/Attachments/Securing%20the%20EHR%20System.
pdf3.
HealthInformationPrivacy-SummaryoftheHIPAASecurityRule.
(n.
d.
).
RetrievedFebruary8,2012,fromU.
S.
DepartmentofHealth&HumanServiceswebsite:http://www.
hhs.
gov/ocr/privacy/hipaa/understanding/srsummary.
html4.
PasswordStrength(n.
d.
).
RetrievedJanuary12,2012,fromWiki-pedia:http://en.
wikipedia.
org/wiki/Password_strength#Guidelines_for_strong_passwords*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof25HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
5.
UniversityofWisconsin-MadisonHIPAASecurityBestPracticesGuidelines,#3AuditControls,4D.
(2004,April13).
RetrievedfromUniversityofWisconsin–Madison:http://hipaa.
wisc.
edu/docs/au-ditControls.
pdfLecture6bCharts,Tables,FiguresNoneinthislecture.
Lecture6bImagesSlide8:VPNexample,2012.
ProvidedbyScottNealSlide10:Firewallexample,2012.
ProvidedbyScottandNolanNealUnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"HardeningServerswithSecurityTemplates"byWindowsSecu-rity.
com,2010,http://www.
windowsecurity.
com/articles/Harden-ing-Servers-Security-Templates.
htmlThisarticleoutlinestheuseofsecuritytemplatesandgrouppolicytohardenserverinfrastructure.
Thearticleprovidesalookintothemanyfaucetsthatmustbecon-sideredwhenimplementingasecureserverstrategy.
2.
"EducatingyourEmployeesonBasicSecurityPrinciples.
"ByDa-vidKelleher;May27,2009[PodcastviatheInternet].
http://www.
net-security.
org/article.
phpid=1241StudentApplicationActivitiescomp8_unit6_activity.
doccomp8_unit6_activity_key.
doccomp8_unit6_self_assess.
doccomp8_unit6_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof26HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit7UnitTitleSystemInterfacesandIntegrationUnitDescriptionThisunitexplorestheissuesandchallengesinvolvedininterfacingandintegratingsystemsincludingunderstandingsystemrequirementsandthemessagingandothertechniquesusedbetweenvarioussystems.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Determineanddocumentsysteminterfacesandintegrationrequire-ments2.
Describethepitfallsassociatedwithinstallinganewapplicationinanenvironmentofpre-existingapplications3.
GiveexamplesofinterfacingmodalitiesUnitTopics/LectureTitles7SystemInterfacesandIntegrationUnitReferences(Alllinksaccessibleasof2/15/2012)Lecture71.
Adler,K.
G.
(2005).
Howtoselectanelectronichealthrecordsystem.
FamPractManag,12(2),55-62.
http://www.
aafp.
org/fpm/2005/0200/p55.
html2.
Chaffee,B.
W.
,&Bonasso,J.
(2004).
Strategiesforpharmacyinte-grationandpharmacyinformation:Technicalaspectsofinterfaces.
AmJHealthSystPharm.
61(5).
http://www.
medscape.
com/viewar-ticle/4712523.
CorepointHealth.
(2010).
Theroleofaninterfaceengineinmodernhealthcare.
http://www.
corepointhealth.
com/whitepapers/role-of-in-terface-engine-in-modern-healthcare*4.
DeSonier,N.
(2006).
WhatiscardinalityinHL7HL7standards.
com.
http://www.
hl7standards.
com/blog/2006/11/02/what-is-hl7-car-dinality/*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof27HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
5.
Zywiak,W.
,&Drazen,E.
(2010).
IntegratingEHRs:HospitaltrendsandstrategiesforinitiatingintegratedEHRswithintheircommuni-ties.
CSC.
com.
http://assets1.
csc.
com/health_services/downloads/CSC_Integrating_EHRs.
pdfLecture7Charts,Tables,Figures7.
1Table.
Neal,S.
,2012.
Lecture7ImagesSlide6:Illustrationsofpoint-to-point&interfaceengine.
ImagescourtesyofScottNeal.
Slide18:HL7interfaceengine.
ImagecourtesyofScottNeal.
Slide21:Point-to-pointEHRinterface.
ImagecourtesyofScottNeal.
Slide22:Point-to-pointvs.
HIEEHRinterfaces.
ImagecourtesyofScottNeal.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"HL7Messages"ByGuntherSchadow.
[Internet],Revised1996,http://aurora.
regenstrief.
org/~gunther/oldhtml/messages.
htmlThisisareferenceguidefordecipheringHL72Xmessages2.
"HL7International.
"[Internet],Revised2010,http://www.
hl7.
org/ThisistheofficialHL7websitewhichhighlightsHL7,discusesHL7asastandardandoutlinestheorganization'sgoalsandachieve-ments.
3.
Interfaceware'swebsiteat:http://www.
interfaceware.
com/hl-7.
htmlThissiteprovidesuserswithanexcellentlaunchingpointforunder-standingtheHL7standardStudentApplicationActivitiescomp8_unit7_activity.
doccomp8_unit7_activity_key.
doccomp8_unit7_self_assess.
doccomp8_unit7_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof28HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit8UnitTitleTroubleshooting,MaintenanceandUpgrades,andInteractionwithVendors,Developers,andUsersUnitDescriptionThisUnitexploresaspectsofsettinguparobustsupportstructurefortroubleshootingandmaintainingthesystem,includingdevelopingtrouble-shootingandescalationprocedures,measuringsystemperformance,andcommunicationwithvendors(orlocaldevelopers).
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Identifyandimplementaneffectivetroubleshootingprocedureforreporting,evaluating,fixing,deploying,andfollow-upoferrors,problems,orlimitationsforthesystem2.
IntegratedowntimescheduleforOS,network,database,andclientapplicationmaintenanceandupdatesUnitTopics/LectureTitles8Troubleshooting,MaintenanceandUpgrades,andInteractionwithVen-dors,Developers,andUsersUnitReferences(Alllinksaccessibleasof1/15/2012)Lecture8a1.
Boyer,E.
andSoback,M.
(2005).
ProductionSupport.
Implement-inganElectronicHealthRecordSystem.
J.
M.
Walker,E.
J.
BieberandF.
Richards,SpringerLondon:95-100.
http://www.
springerlink.
com/content/n520ghg078416463/2.
Felt-Lisk,S;Johnson,L;Fleming,C;Shapiro,R;Natzke,B.
2009September22[Internet].
.
TowardunderstandingEHRuseinsmallphysicianpractices.
Availablefrom:http://www.
thefreelibrary.
com/Toward+understanding+EHR+use+in+small+physician+practic-es.
-a02166321343.
Heubusch,K.
"PhysicianPracticesandInformationManagement:HIMProfessionalsOfferValueinChangingPractices.
"JournalofAHIMA79,no.
8(August2008):18-22.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof29HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
4.
Lake,T,Collins,T,andGinsburg,P(2011).
"FosteringHealthInfor-mationTechnologyinSmallPhysicianPractices:LessonsfromIn-dependentPracticeAssociations".
NationalInstituteforHealthCareReform.
[Internet].
http://www.
nihcr.
org/HIT-and-IPAs.
html.
5.
Pereira,P(2010).
"AfterEHRsystemimplementation,maintenance,servicequestionsremain",SearchHealthIT.
[Internet].
http://searchhealthit.
techtarget.
com/news/2240020962/After-EHR-sys-tem-implementation-maintenance-service-questions-remainLecture8aCharts,Tables,FiguresNoneinthislecture.
Lecture8aImagesSlide8:"EHRTroubleshootingWorkflow"byScottNeal.
UsedwithPer-missionLecture8b1.
Boyer,E.
andM.
Soback(2005).
ProductionSupport.
ImplementinganElectronicHealthRecordSystem.
J.
M.
Walker,E.
J.
BieberandF.
Richards,SpringerLondon:95-100.
http://www.
springerlink.
com/content/n520ghg078416463/2.
"EventTracingforWindows"(2011).
Microsoft.
com.
[Internet]].
http://msdn.
microsoft.
com/en-us/library/ff545699.
aspx.
3.
"GuidetoReducingUnintendedConsequencesofElectronicHealthRecords"(2011).
AHRQ.
[Internet].
http://www.
ucguide.
org/4.
Halamka,John.
"10tipsfortroubleshootingcomplexEHRinfra-structureproblems".
KevinMD.
com.
[Internet].
http://www.
kevinmd.
com/blog/2010/09/10-tips-troubleshooting-complex-ehr-infra-structure-problems.
html.
5.
"SQLServerSecurity,Performance&Tuning.
"(2009).
SSQA.
net.
[Internet].
http://sqlserver-qa.
net/blogs/perftune/ar-chive/2009/07/26/5820.
aspx*6.
"TechnicalComparisonofOracleDatabase10gandSQLServer2005:FocusonManageability,May2005"(2005,May).
Oracle.
[In-ternet].
http://www.
oracle.
com/technetwork/database/focus-areas/manageability/ss-1.
pdf7.
Wunder,Bill"BenchmarkingTechniquesUsingT-SQLPart1-Sys-temStatisticalFunctional".
[Internet].
http://64.
29.
220.
154/articles/viewarticle.
aspxid=17797*.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof30HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Lecture8bCharts,Tables,FiguresNoneinthislecture.
Lecture8bImagesNoneinthislecture.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"TrytheseEfficiencyStrategiesWhenSettingUpaHelpdesk"byTechrepublic.
com,2004,http://articles.
techrepublic.
com.
com/5100-10878_11-5112468.
htmlThisarticlegoesthrough5stepsof.
Set-tingupaneffectiveandsuccessfulhelpdeskfromthegroundup.
2.
"EducatingyourEmployeesonBasicSecurityPriciples.
"ByDa-vidKelleher;May27,2009[PodcastviatheInternet].
http://www.
net-security.
org/article.
phpid=124StudentApplicationActivitiescomp8_unit8_activity.
doccomp8_unit8_activity_key.
doccomp8_unit8_self_assess.
doccomp8_unit8_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof31HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit9UnitTitleCreatingFaultTolerantSystems,Backups,andDecommissioningUnitDescriptionUnitdescriptiongoeshere.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Defineavailability,reliability,redundancy,andfaulttolerance2.
Explainareasandoutlinerulesforimplementingfaulttoler-antsystems3.
Performriskassessment4.
Followbestpracticeguidelinesforcommonimplementations5.
Developstrategiesforbackupandrestoreofoperatingsystems,applications,configurationsettings,anddatabasesand6.
DecommissionsystemsanddataUnitTopics/LectureTitles9a1.
CreatingFaultTolerantSystems,Backups,andDecommissioning9a2.
CreatingFault-TolerantSystems,Backups,andDecommissioning9a3.
CreatingFault-TolerantSystems,Backups,andDecommissioningUnitReferences(Alllinksaccessibleasof2/17/2012(9a)and2/17/2012(9b))Lecture9a1.
BensonC.
SecurityPlanning.
(n.
d.
)Availablefrom:http://technet.
microsoft.
com/en-us/library/cc723503.
aspx2.
Maniscalchi,J.
Threatvs.
Vulnerabilityvs.
Risk.
(June2009)Availablefrom:http://www.
digitalthreat.
net/2009/06/threat-vs-vulnerability-vs-risk/3.
AConceptualFrameworkforSystemFaultTolerance-1.
1WhatisaSystem(1995,March30).
RetrievedfromNation-alInstituteofStandardsandTechnologywebsite:http://his-sa.
nist.
gov/chissa/SEI_Framework/framework_3.
htm**Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof32HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
4.
AConceptualFrameworkforSystemFaultTolerance-5Put-tingItAllTogether(1995,March30).
RetrievedfromNationalInstituteofStandardsandTechnologywebsite:http://hissa.
nist.
gov/chissa/SEI_Framework/framework_20.
html*5.
ServerAvailabilityTrendsInTheTimeOfElectronicHealthRecords.
(January2010)ForresterResearch,Inc.
Availableathttp://www.
himss.
org/content/files/Stratus%20Tech%20-%20ServerAvailabilityTrends_EHR_ForresterPaper.
pdf*Acknowledgement:Thefollowingreferencegenerallyinformedtheunit1.
Shackhow,T.
etal.
(June2008).
EHRMeltdown:HowtoProtectYourPatientData.
FamPractManag,15(6),A3-A8.
Availablefrom:http://www.
aafp.
org/fpm/2008/0600/pa3.
htmlLecture9aCharts,Tables,FiguresNoneinthislecture.
Lecture9aImagesNoneinthislecture.
Lecture9b1.
RAID[cited2012January31].
Retrievedfrom:http://en.
wikipedia.
org/wiki/RAID2.
Sanford,R.
(April2010)ElectronicHealthRecordsNeedaFail-ProofFoundationtoDeliveronQuality,EconomyPromises.
"HealthNewsDigest.
Availablefrom:http://www.
healthnewsdigest.
com/news/Guest_Columnist_710/Electronic_Health_Records_Need_a_Fail-Proof_Foundation_to_Deliver_on_Quality_Economy_Promises_2_printer.
shtml3.
Tulloch,M.
(April2005)"ImplementingFaultToleranceonWindowsNetworks".
Availablefrom:http://www.
windowsnetworking.
com/articles_tutorials/Implementing-Fault-Tolerance-Windows-Networks.
htmlAcknowledgement:Thefollowingreferencegenerallyinformedtheunit1.
Shackhow,T.
etal.
(June2008).
EHRMeltdown:HowtoProtectYourPatientData.
FamPractManag,15(6),A3-A8.
Availablefrom:http://www.
aafp.
org/fpm/2008/0600/pa3.
htmlLecture9bCharts,Tables,FiguresNoneinthislecture.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof33HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Lecture9bImagesSlide5:RAID0,RAID1,RAID5,RAID6[en:User:Cburnett].
c2006[up-dated2000Jan28;cited2006Feb15].
Availablefrom:http://commons.
wikimedia.
org/wiki/Redundant_array_of_independent_disksLecture9cHarwood,M.
(2003,September24).
StorageBasics:BackupStrategies.
RetrievedfromEnterpriseStorageForum.
comwebsite:http://hissa.
nist.
gov/chissa/SEI_Framework/framework*http://www.
enterprisestorageforum.
com/management/features/article.
php/3082691_3.
html*SurvivingaBottleneck-InsightsintoManagingExponentialGrowthofDigitizedMedicalImages.
(2009,March16).
RetrievedfromScicastswebsite:asts.
com/specialreports/86-healthcare-it/2442-surviving-a-bottle-neck-insights-into-managing-exponential-growth-of-digitized-medical-im-agesGordon,S.
(n.
d.
).
Comparingdifferentbackupstrategies.
RetrievedFebru-ary8,2007,fromSearchStoragewebsite:http://searchstorage.
techtarget.
com/tip/Comparing-different-backup-strategiesPracticeBrief-RetentionofHealthInformation(updated)-Table4:StateLawsorRegulationsPertainingtoRetentionofHealthInformation.
(n.
d.
).
RetrievedFebruary8,2012,fromAHIMAwebsite:http://library.
ahima.
org/xpedio/groups/public/documents/ahima/bok1_012547.
pdf*Lecture9cCharts,Tables,FiguresNoneinthislecture.
Lecture9cImagesNoneinthislecture.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"EHRMeltdown:HowtoProtectYourPatientData:Sidebar:ImplementingaThree-DimensionalBackupPlan"byDrs.
Schackow,Palmer,andEpperly,2008,http://www.
medscape.
com/viewarticle/579131_sidebar2*Anexcellentarticleoutlining23differentbackupstrategiesforEHRsystems.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof34HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
2.
"FaultToleranttechniquesforDistributedSystems"ByBrianSetlic;Jul.
27,2004[Internet].
http://www.
ibm.
com/developerworks/rational/library/114.
html*Thisarticleoutlinesconceptsbehindfaulttolerantcomputing,generalfaulttoleranceprocedures,dependency,distributedsystems,andcreatingfaulttolerantpatternsfordistributedsystems.
3.
"EnhancedServerToleranceforImprovedUserExperience"byManishMarwah,ShivakantMishra,andChristofFetzer,June2008;[ArticleavailableviaInternet]http://www.
cs.
colorado.
edu/~mishras/research/papers/dsn08.
pdfStudentApplicationActivitiescomp8_unit9_activity.
doccomp8_unit9_activity_key.
doccomp8_unit9_self_assess.
doccomp8_unit9_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof35HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit10UnitTitleDevelopingaTestStrategyandaTestPlanUnitDescriptionThisUnitexploresaspectsoftestingthesystem,includingtheuseofper-formancebaselinesandtheroleoftestplans.
UnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Gatheruserfeedbackandperformancebaselineforsystemvalidationandtesting2.
Documentproblemswiththeirresolutionstatus3.
Create,execute,anddocumentatestplanUnitTopics/LectureTitles10DevelopingaTestStrategyandaTestPlanUnitReferences(Alllinksaccessibleasof2/27/2012)Lecture101.
""Acceptancetesting"(2011).
Wikipedia.
[Internet]http://en.
wikipe-dia.
org/wiki/Acceptance_testing.
2.
Kumar,K.
(2007,May18).
BeginnersGuideToSoftwareTest-ing.
RetrievedFebruary10,2012,fromKRTestingSolutionswebsite:http://kuldeepse.
wordpress.
com/2007/05/18/begin-ners-guide-to-software-testing-i/3.
Tucker,J.
(2003,September).
Definition-smoketesting.
RetrievedFebruary10,2012,fromSearchWinDevelopmentwebsite:http://searchwindevelopment.
techtarget.
com/definition/smoke-testing4.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
Re-trievedfromPROJECTPERFECTwebsite:http://www.
projectper-fect.
com.
au/downloads/Info/info_test_strategy.
pdf5.
WhatisAcceptanceTesting.
(n.
d.
).
RetrievedFebruary10,2012,fromwiseGEEK-ConjectureCorporationwebsite:http://www.
wise-geek.
com/what-is-acceptance-testing.
htm.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof36HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Lecture10Charts,Tables,Figures10.
1Table.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
RetrievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
2Table.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
Re-trievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
3Table.
,N.
(2006,January30).
DevelopingaTestStrategy.
RetrievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
4Table.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
Re-trievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
5Table.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
Re-trievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
6Table.
Turbit,N.
(2006,January30).
DevelopingaTestStrategy.
Re-trievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/downloads/Info/info_test_strategy.
pdf10.
7Table.
Kumar,K.
(2007,May18).
BeginnersGuideToSoftwareTesting.
RetrievedFebruary10,2012,fromKRTestingSolutionsweb-site:http://kuldeepse.
wordpress.
com/2007/05/18/beginners-guide-to-soft-ware-testing-i/andTurbit,N.
(2006,January30).
DevelopingaTestStrategy.
RetrievedfromPROJECTPERFECTwebsite:http://www.
projectperfect.
com.
au/down-loads/Info/info_test_strategy.
pdfLecture10ImagesNoneinthislecture.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"Testing:TestPlandevelopment"byCraigBorysowich.
February2005;[Internet].
http://it.
toolbox.
com/blogs/enterprise-solutions/testing-test-plan-development-step-1-2923Thisonlineresourceoutlinesthe10stepstodevelopingatestplan…fromassemblingtheteamtoanalyzingthereports.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof37HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
2.
"HowtodoSoftwareUsertesting(UAT)ReallyBadly";[Internet].
http://www.
eviltester.
com/index.
php/2008/03/07/how-to-do-software-user-acceptance-testing-uat-really-badly/Thisauthortakesamore–tongue–in-cheekapproachtousertestingbyoutliningthingsdonewrongoveryearsofUATtestingexperiences.
3.
"WhatisUserAcceptanceTesting.
"ByExforsys.
[Internet].
http://www.
exforsys.
com/tutorials/testing/what-is-user-acceptance-testing.
htmlThisarticledefinesusertestinganddiscusseseachofthefundamentaltasks.
4.
"HowtoPlanaUserAcceptanceTest.
"ByTammyClevenger,eHow.
[Internet].
http://www.
ehow.
com/how_5245146_plan-user-acceptance-test.
htmlThisarticleoutlines11stepsforplanningauseracceptancetest.
5.
"UserAcceptanceTestPlan.
"ByUniversityofMinnesota.
[Internet].
www.
uservices.
umn.
edu/pmo/docs/Test/TEMPLATE_UAT_Plan.
doc*Thisisasampletestplantemplate.
StudentApplicationActivitiescomp8_unit10_activity.
doccomp8_unit10_activity_key.
doccomp8_unit10_self_assess.
doccomp8_unit10_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof38HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Component8/Unit11UnitTitlePilotTestingandFull-ScaleDeploymentUnitDescriptionThisUnitexploresaspectsofdeployingthesystemtoendusers,includingcommunication,technicalsupport,userfeedback,andsystemresourceevaluationincludinginitialpilottestingtoobtainfeedbackbeforefulldeployment,includingplanning,identifyingtheusergroup,settingupthesystem,andgatheringfeedbackUnitObjectivesBytheendofthisunitthestudentwillbeableto:1.
Identifypilottesting,deploymentsteps,andgroupforpilottesting2.
Developaplanfortrainingpilotusers3.
Gatherandprioritizefeedbackfrompilottest4.
Recommendamountoflegacydatatopreload5.
Developaplanforimplementationusingbestpractices6.
Identifypost-implementationpracticesUnitTopics/LectureTitles11PilotTestingandFull-ScaleDeploymentUnitReferences(Alllinksaccessibleasof2/10/2012)Lecture111.
Adler,K.
(2007February).
HowtoSuccessfullyNavigateYourEHRImplementation.
FamPractManag.
,14(2),33-39.
Retrievedfromhttp://www.
aafp.
org/fpm/2005/0200/p55.
html2.
EHRAdoption-Implementing.
(n.
d.
).
RetrievedFebruary9,2012,fromRhodeIslandQualityInstitutewebsite:http://www.
docehrtalk.
org/benefits-adoption/implementing3.
Fullerton,C.
,Aponte,P.
,HopkinsIII,R.
,Bragg,D.
,&Ballard,D.
J.
(2006).
Lessonslearnedfrompilotsiteimplementationofanambulatoryelectronichealthrecord.
Proc(BaylUnivMedCent),19,303-310.
Retrievedfromhttp://www.
baylorhealth.
edu/Documents/BUMC%20Proceedings/2006%20Vol%2019/No.
%204/19_4_Fullerton.
pdf*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof39HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
4.
Huffmaster,T.
,&Holmes,M.
L.
(2008,June18).
SelectingandImplementingaCommunitywideEHR,Part2.
RetrievedfromHospitals&HealthNetworks(H&HN)website:http://www.
hhnmag.
com/hhnmag_app/jsp/articledisplay.
jspdcrpath=HHNMOSTWIRED/Article/data/Spring2008/080618MW_Online_Huffmaster&domain=HHNMOSTWIRED*5.
TheDesignandImplementationofaComputerizedPatientRecordattheOhioStateUniversityHealthSystem–ASuccessStory.
(2001DaviesOrganizationalAwardWinners).
(2001).
RetrievedfromHIMSSwebsite:http://www.
himss.
org/content/files/davies_2001_osuhs.
pdf*Lecture11Charts,Tables,FiguresNoneinthislecture.
Lecture11ImagesNoneinthislecture.
UnitRequiredReadingsNoneinthislecture.
UnitSuggestedReadings1.
"CreatingaNewSoftwarePlan"byBrienM.
Posey.
2016;[Internet].
http://articles.
techrepublic.
com.
com/5100-10878_11-6130373.
htmlBrienPoseydiscusseshowtodesignatypicalsoftwaredevelopmentplanwithemphasisonpilottesting,fororganizationalrollouts.
2.
"Workflow-theKeyIngredientinDeployingEHRandCPOESystems(twoparts).
"2010;[Internet].
http://www.
santarosaconsulting.
com/SantaRosaTeamBlog/post/2010/02/11/Workflow.
aspxhttp://www.
santarosaconsulting.
com/SantaRosaTeamBlog/post/2010/02/17/Workflow-The-Key-Ingredient-in-Deploying-EHR-and-CPOE-Systems-Part-11.
aspxThisarticle(part1and2)emphasizestheimportanceofanalyzingworkflowdesignasakeyingredientindeployingEHRsystems.
*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof40HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
3.
"SelectingandImplementingaCommunitywideEHRParts1and2.
"".
ByJoeSofianekandMichelleL.
Holmes;[Internet].
http://www.
hhnmostwired.
com/hhnmostwired_app/jsp/articledisplay.
jspdcrpath=HHNMOSTWIRED/Article/data/Spring2008/080611MW_Online_Sofianek&domain=HHNMOSTWIREDhttp://www.
hhnmag.
com/hhnmag_app/jsp/articledisplay.
jspdcrpath=HHNMOSTWIRED/Article/data/Spring2008/080618MW_Online_Huffmaster&domain=HHNMOSTWIRED*StudentApplicationActivitiescomp8_unit11_activity.
doccomp8_unit11_activity_key.
doccomp8_unit11_self_assess.
doccomp8_unit11_self_assess_key.
doc*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof41HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
ComponentAcronymGlossaryDCHIAcronymGuide(January2011)AcronymNameAAFPAmericanAcademyofFamilyPhysiciansABIMAmericanBoardofInternalMedicineACKAcknowledgment(Datanetworks)ACLsAccessControlListsACMAssociationforComputingMachineryACMIAmericanCollegeofMedicalInformaticsACRAmericanCollegeofRadiologyADaMAnalysisDataModel(ADaM)ADAAmericanDentalAssociationADEsAdverseDrugEventsADRAdverseDrugReactionADTAdmissions,Discharge,TransferAHICAmericanHealthInformationCommunityAHIMAAmericanHealthInformationManagementAssociationAHIPAmerica'sHealthInsurancePlansAHRQAgencyforHealthcareResearchandQualityAMAmplitudeModulationAMAAmericanMedicalAssociationAMIAAmericanMedicalInformaticsAssociationANSIAmericanNationalStandardsInstituteAPIApplicationProgrammingInterfacesARRAAmericanRecoveryandReinvestmentActASCX12AccreditedStandardsCommitteeASTMAmericanSocietyforTestingAndMaterialsASQAmericanSocietyforQualityATAAmericanTelemedicineAssociationATCBAuthorizedTestingandCertificationBodiesATMAsynchronousTransferModeAUPAcceptableUsePolicyBCMABarCodeMedicationAdministrationBCPBusinessContinuityPlanningBISBispectralIndexBMIBodyMassIndexbpsBitsPerSecondBRIDGBiomedicalResearchIntegratedDomainGroupBSABodySurfaceArea*Indicatesthislinkisnolongerfunctional.
HealthITWorkforceCurriculumInstallationandMaintenanceof42HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
BSLMBioinformaticSequenceMarkupLanguageCACertificateAuthorityCaDSRCancerDataStandardRepositoryCAPCollegeofAmericanPathologistsCBACabarrusHealthAllianceCCDContinuityofCareDocumentCCHITCertificationCommissionforHealthcareInformationTechnologyCCOWClinicalContextObjectWorkgroup(HL7)CCRContinuityofCareRecordCDAClinicalDocumentArchitectureCDASHClinicalDataAcquisitionStandardsHarmonizationCDCCentersforDiseaseControlandPreventionCDECommonDataElementsCDISCClinicalDataInterchangeStandardsConsortiumCDMChronicDiseaseManagementCDSClinicalDecisionSupportCDSRCochraneDatabaseofSystematicReviewsCDSSClinicalDecisionSupportSystemCENEuropeanCommitteeforStandardizationCGClinicalGenomicsCHFCongestiveHeartFailureCHIConsumerHealthInformaticsCICAContextInspiredComponentArchitectureCISClinicalInformationSystemCMETCommonMessageElementTypeCMMCapabilityMaturityModelCMMICapabilityMaturityModelIntegrationCMSCentersforMedicareandMedicaidServicesCOPDChronicObstructivePulmonaryDiseaseCOTSCommercialOff-the-ShelfCPMCommonProductModelCPOEComputerizedProviderOrderEntryCPTCurrentProceduralTerminologyCQIConsumerQualityInitiativesCRLCertificateRevocationListCRTCathodeRayTubeCSIComputableSemanticInteroperabilityCSMA/CACarrierSenseMultipleAccess/CollisionAvoidanceCSMA/CDCarrierSenseMultipleAccess/CollisionDetectionHealthITWorkforceCurriculumInstallationandMaintenanceof43HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
CTComputedTomographyCTACenterforTechnologyandAgingCTSAClinicalTranslationalScienceActCWMCommonWarehouseModelDACDiscretionaryAccessControlDAMDomainAnalysisModelDFDsDataFlowDiagramsDHCPDynamicHostConfigurationProtocolDHHSDepartmentofHealthandHumanServicesDICOMDigitalImagingandCommunicationsinMedicineDMAICDefine,Measure,Analyze,Improve,ControlDMIMDomainMessageInformationModelDNSDomainNameServiceDoDDepartmentofDefenseDoSDenialofServiceDRGDiagnosis-relatedGroupDSLDigitalSubscriberLineDSSDecisionSupportSystemDSTUDraftStandardforTrialUseDTDDocumentTypeDefinitionDURSADataUseandReciprocalSupportAgreementEAEnterpriseArchitectureEBMEvidenceBasedMedicineECGElectrocardiographyEDEmergencyDepartmentEDIElectronicDataInterchangeEDMSElectronicDocumentManagementSystemEEGElectroencephalogramEHRElectronicHealthRecordsEHR-FMElectronicHealthRecord-SystemsFunctionalModelEHR-SElectronicHealthRecord-SystemsEHRVAElectronicHealthRecordVendorsAssociationeMARMedicationAdministrationRecordsEMEAEuropeanMedicinesAgencyEMIElectromagneticInterferenceeMRElectronicMedicalRecordsEMRElectronicMedicalRecords/PatientManagementEMR/PMElectronicProtectedHealthInformationePHIEnterpriseMasterPatientIndexEPMIElectronicPrescribingHealthITWorkforceCurriculumInstallationandMaintenanceof44HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
E-REntity-RelationshipERDsEntity-RelationshipDiagramseRXElectronicPrescribingEVSEnterpriseVocabularyServiceFACAFederalAdvisoryCommitteeActFDAFoodandDrugAdministrationFDDIFiberDataDistributedInterfaceFERPAFamilyEducationalRightsandPrivacyActFMFrequencyModulationFMEAFailureModeandEffectsAnalysisFTPFileTransferProtocolFQHCFederallyQualifiedHealthCenterGDSNGlobalDataSynchronisationNetworkGELLOanobject-orientedexpressionlanguageforclinicaldecisionsupportGEMGuidelineElementsModelGINGenericIncidentNotificationGISGeographicInformationSystemGLIFGuideLineInterchangeFormatHCDHumanCenteredDesignHCISHealthCareInformationSystemHDCHealthDisparitiesCollaborativeHDFHierarchicalDataFormatHHSU.
S.
DepartmentofHealthandHumanServicesHIEHealthInformationExchangeHIMHealthInformationManagementHIMSSHealthInformationandManagementSystemsSocietyHIPAAHealthInsurancePortabilityandAccountabilityActHISHealthInformationSystemorHospitalInformationSystemsHISPCHealthInformationSecurityandPrivacyCollaborationHITHealthInformationTechnologyHITECHHealthInformationTechnologyforEconomicandClinicalHealthHITPCHealthInformationTechnologyPolicyCommitteeHITSCHealthInformationTechnologyStandardsCommitteeHITSPHealthInformationTechnologyStandardsPanelHL7HealthLevelSevenHMDHierarchicalMessageDescriptionsHRSAHealthResourcesandServicesAdministrationHealthITWorkforceCurriculumInstallationandMaintenanceof45HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
HSSPHealthcareServicesSpecificationProjectHTTPHypertextTransferProtocolHWHardwareHzHertzIANAInternetAssignedNumbersAuthorityICDInternationalClassificationofDiseasesICD-10-CMInternationalClassificationofDiseases,10thRevision,ClinicalModificationICHInternationalConferenceonHarmonisationofTechnicalRequirementsforRegistrationofPharma-ceuticalsforHumanUseICMPInternetControlMessageProtocolICPCInternationalClassificationofPrimaryCareICSRIndividualCaseSafetyReportICTInformationandCommunicationTechnologiesICUIntensiveCareUnitIDSIntrusionDetectionSystemIEInternetExplorerIECInternationalElectrotechnicalCommissionIEEEInstituteofElectricalandElectronicsEngineersIETFInternetEngineeringTaskForceIGImplementationGuide(HL7)IHEIntegratingtheHealthcareEnterpriseIHSIndianHealthServicesIHTSDOInternationalHealthTerminologyStandardsDevelopmentOrganisationIISInternetInformationServicesINRInternationalNormalizedRatioIOMInstituteofMedicineIPInternetProtocolIP/OPInpatient/OutpatientISInformationSystemISDNIntegratedServicesDigitalNetworkISOInternationalOrganizationforStandardizationISO/TCInternationalOrganizationforStandardization's(ISO)TechnicalCommittee(TC)onhealthinformaticsITInformationTechnologyITSImplementableTechnologySpecifications(HL7)JICJointInitiativeCouncilLABLaboratoryDataModelHealthITWorkforceCurriculumInstallationandMaintenanceof46HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
LANLocalAreaNetworkLDAPLightweightDirectoryAccessProtocolLeapfrogGroupConsortiumofmajorcompaniesandotherlargeprivateandpublichealthcarepurchasersLIMSLabInformationManagementSystemLLCLogicalLinkControlLOINCLogicalObservationIdentifiersNamesandCodesMACMandatoryAccessControlMARMedicationAdministrationRecordMDMedicalDoctorMDAModelDrivenArchitectureMDEMasterDataElementMDFMethodologyDevelopmentFrameworkMDMMasterDataManagementMEDCINSystemofstandardizedmedicalterminologydevel-opedbyMedicompSystemsMedDRAMedicalDictionaryforRegulatoryActivitiesMICRMultipurposeInternetMailExtensionsMIMEMagneticInkCharacterRecognitionMISManagementInformationSystemMLMMedicalLogicModuleMLLPMinimalLowerLayerProtocolMMAMedicarePrescriptionDrug,Improvement,andModernizationActorMedicareModernizationActMMISMedicaidManagementInformationSystemMOTSModifiableOff-the-ShelfMPIMasterPatientIndexMSHMessageHeaderSegmentMUMeaningfulUseNAHITNationalAllianceforHealthInformationTechnologyNATNetworkAddressTranslationNCPDPNationalCouncilforPrescriptionDrugProgramsNCINationalCancerInstituteNCI-CBIITNationalCommitteeonVitalHealthStatisticsNCVHSNationalCancerInstituteCenterforBioinformaticsandInformationTechnologyNDCNationalDrugCodesNDFNationalDrugFileNDF-RTNationalDrugFile-ReferenceTerminologyNEMANationalElectricalManufacturersAssociationHealthITWorkforceCurriculumInstallationandMaintenanceof47HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
NEDSSNationalElectronicDiseaseSurveillanceSystemNETSSNationalElectronicTelecommunicationsSystemforSurveillanceNetBUINetBiosExtendedUserInterfaceNGCNationalGuidelineClearinghouseNHIMGNationalHealthInformationManagementGroupNICNetworkInterfaceCardsNIHNationalInstitutesofHealthNISTNationalInstituteforStandardsandTechnologyNIST-ATLNationalInstituteforStandardsandTechnology-Ad-vancedTechnologyLaboratoriesNHINNationwideHealthInformationNetworkNLBNetworkLoadBalancingNLMNationalLibraryofMedicineNPINationalProviderIdentifierNRZNonReturntoZeroNTFSNewTechnologyFileSystemNQFNationalQualityForumOASISOrganizationfortheAdvancementofStructuredInfor-mationStandardsOCCOfficeofCareCoordinationOCLObjectConstraintLanguageOCROfficeofCivilRightsODMOperationalDataModelorOpticalCharacterRecogni-tionOIDObjectIdentifierOLAPOnlineAnalyticalProcessingOMGObjectManagementGroupONCOfficeoftheNationalCoordinatorforHealthInforma-tionTechnologyONC-ATCBOfficeoftheNationalCoordinatorAuthorizedTestingandCertificationBodyOODOperatingRoomORObjectOrientedDesignOSOperatingSystemOSIOpenSystemsInterconnectionOTPOne-TimePasswordsOUIOrganizationalUniqueIdentifierOWLWebOntologyLanguagePACSPictureArchivingandCommunicationSystemsHealthITWorkforceCurriculumInstallationandMaintenanceof48HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
PBMSPharmacyBenefitManagersPCIPeripheralComponetInterconnectPCTPrimaryCareTrustPDAsPortableDigitalAssistantsorPersonalDigitalAssis-tantsPDCAPlan–Do–Check–ActPDSAPlan-Do-Study-ActPDUsProtocolDataUnitsPHDSCPublicHealthDataStandardsConsortiumPHERPublicHealthEmergencyResponsePHIProtectedHealthInformationPHIIPersonalHealthRecordPHRPubicHealthInformaticsInstitutePHR-FMPersonalHealthRecord-FunctionalModelPICProcessImprovementCommittee(HL7)PIXPatientIdentifierCross-ReferencingPKIPublicKeyInfrastructurePMProjectManagementPMHPastMedicalHistoryPMIPatientMasterIndexPMSPracticeManagementSystemPOPPostOfficeProtocolPPPPoint-to-PointProtocolQAPQualityAssuranceProjectQFDQualityFunctionDeploymentQIQualityImprovementRARegistrationAuthorityR-ADTReservation/Registration-Admission,Discharge,TransferRAIDRedundantArrayofIndependentDisksRAMRandomAccessMemoryRBACRoleBasedAccessControlRCRIMRegulatedClinicalResearchInformationManagementRELMARegenstriefLOINCMappingAssistantRFRadioFrequencyRFIRadioFrequencyInterferenceRFIDRadioFrequencyIdentifiersRFPRequestForProposalRHIOsRegionalHealthInformationOrganizationsRIMReferenceInformationModelHealthITWorkforceCurriculumInstallationandMaintenanceof49HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
RISRadiologyInformationSystemsRMIMRefinedMessageInformationModelRMPIRegistryMasterPatientIndexROIReturnOnInvestmentRPMRemotePatientMonitoringRPSRegulatedProductSubmissionRSNARadiologicalSocietyofNorthAmericaRXPrescriptionSAEAFServices-AwareEnterpriseArchitectureFrameworkSAIFServicesAwareInteroperabilityFrameworkSANStorageAreaNetworkSATASerialAdvancedTechnologyAttachmentSCOSDOCharterOrganizationSCSISmallComputerSystemInterfaceSDLCSoftwareDevelopmentLifeCycleSDMSystemsDevelopmentMethodSDOStandardDevelopmentOrganizationSDTMStudyDataTabulationModelSEISubjectMatterExpertSMESoftwareEngineeringInstituteSMTPSimpleMailTransportProtocolSNOMEDSystematizedNomenclatureofMedicineSNOMEDCTSystematizedNomenclatureofMedicine--ClinicalTermsSNOMEDRTSystematizedNomenclatureofMedicine--ReferenceTerminologySNOPSystematizedNomenclatureofPathologySOAServiceOrientedArchitectureSOAPSimpleObjectApplicationProtocolSOPStructuredProductLabelingSPCStatisticalProcessControlSPLStandardOperatingProcedureSSASocialSecurityAdministrationSSIDServiceSetIdentifierSSLSecureSocketLayerSSNSocialSecurityNumberSSOSingleSign-OnSTPShieldedTwisted-PairTCP/IPTransmissionControlProtocol/InternetProtocolTEPRTowardanElectronicPatientRecordConferenceHealthITWorkforceCurriculumInstallationandMaintenanceof50HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
TLSTransportLayerSecurityTOCTableofContentsTPTwisted-PairTPSTransactionProcessingSystemTSCHL7TechnicalSteeringCommitteeTTLTimetoLiveUATUserAcceptanceTestingUDPUserDatagramProtocolUMLUniformModelingLanguageUMLSUnifiedMedicalLanguageSystemURLsUniversalResourcesLocatorsUPIUniquePatientIdentifierUPSUn-interruptedpowersupplyUSUltrasoundUSBUniversalSerialBusUSTAGU.
S.
TechnicalAdvisoryGroupUTPUnshieldedTwisted-PairVAVeteransAdministrationVA_NDF-RTVeteransAdministrationNationalDrugFile-ReferenceTerminologyvMRVirtualMedicalRecordVPNVirtualPrivateNetworkVSSVolumeShadowCopyServiceVUHIDVoluntaryUniversalHealthcareIdentificationSystemVUMCVanderbiltUniversityMedicalCenterW3CWorldWideWebConsortiumWANWideAreaNetworkWAPWirelessAccessPointWHOWorldHealthOrganizationWLANWirelessLocalAreaNetworkWONCAWorldOrganizationofNationalColleges,AcademiesandAcademicAssociationsofGeneralPractitioners/FamilyPhysicians.
(WorldOrganizationofFamilyDoc-tors)WSDLWebServicesDescriptionLanguageWWWWorldWideWebXDRExternalDataRepresentationXMLExtensibleMarkupLanguageHealthITWorkforceCurriculumInstallationandMaintenanceof51HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
CreativeCommonsAttribution-NonCommercial-ShareAlike3.
0Un-portedCCBY-NC-SAThisworkislicensedundertheCreativeCommonsAttribution-NonCommer-cial-ShareAlike3.
0UnportedLicense.
Toviewacopyofthislicense,visithttp://creativecommons.
org/licenses/by-nc-sa/3.
0/orsendalettertoCreativeCom-mons,171SecondStreet,Suite300,SanFrancisco,California,94105,USA.
DETAILSoftheNonCommercial-ShareAlike3.
0Unportedlicense:Youarefree:toShare—tocopy,distributeandtransmittheworktoRemix—toadapttheworkUnderthefollowingconditions:Attribution—Youmustattributetheworkinthemannerspecifiedbytheauthororlicensor(butnotinanywaythatsuggeststhattheyendorseyouoryouruseofthework):Courtesyof(nameofuniversitythatcreatedthework)andtheONCHealthITWorkforceCurriculumprogram.
Noncommercial—Youmaynotusethisworkforcommercialpurposes.
Note:Useofthesematerialsisconsidered"non-commercial"foralleducationalinstitutions,foreducationalpurposes,includingtuition-basedcourses,continuingeducationscourses,andfee-basedcourses.
Thesellingofthesematerialsisnotpermitted.
Chargingtuitionforacourseshallnotbeconsideredcommercialuse.
ShareAlike—Ifyoualter,transform,orbuilduponthiswork,youmaydistrib-utetheresultingworkonlyunderthesameorsimilarlicensetothisonewiththeunderstandingthat:Waiver—Anyoftheaboveconditionscanbewaivedifyougetpermissionfromthecopyrightholder(theuniversitythatcreatedthework).
PublicDomain—Wheretheworkoranyofitselementsisinthepublicdomainunderapplicablelaw,thatstatusisinnowayaffectedbythelicense.
OtherRights—Innowayareanyofthefollowingrightsaffectedbythelicense:Yourfairdealingorfairuserights,orotherapplicablecopyrightexceptionsandlimitations;Theauthor'smoralrights;Rightsotherpersonsmayhaveeitherintheworkitselforinhowtheworkisused,suchaspublicityorprivacyrights.
Notice—Foranyreuseordistribution,youmustmakecleartootherstheli-censetermsofthiswork.
Thebestwaytodothisiswithalinktothiswebpage(http://creativecommons.
org/licenses/by-nc-sa/3.
0/).
ToviewtheLegalCodeofthefulllicense,followthislink:http://creativecommons.
org/licenses/by-nc-sa/3.
0/legalcodeHealthITWorkforceCurriculumInstallationandMaintenanceof52HealthITSystemsVersion3.
0/Spring2012ThismaterialwasdevelopedbyDukeUniversity,fundedbytheDepartmentofHealthandHumanServices,OfficeoftheNa-tionalCoordinatorforHealthInformationTechnologyunderAwardNumberIU24OC000024.
Appendix1:SunnyHappyCareFamilyPracticeScenarioActivitieshavebeencreatedthroughoutthiscomponentreferencingSun-nyHappyCaretoprovideamorerelevantandconsistentexperienceforthestudent.
Theexamplewasintentionallywrittentoprovideflexibilityfortheinstructor,whocantailortheexampletobestmeetthespecificneedsforthecomponent.
TheSunnyHappyCaredocumentationincludes:AnintroductorylectureoutliningSunnyHappyCareFamilyPractice(SHCFP)NotesandguidelinesforusingSHCFPdocumentsFloorPlansforSHCFP,onewithnetworkingports,onewithout.
Thesedocumentscanbefoundinthezipwithfilename:comp8_SHC_scenario.
zip