https://wiki.galenhealthcare.com/api.php?action=feedcontributions&user=Justin.Campbell&feedformat=atomGalen Healthcare Solutions - Allscripts TouchWorks EHR Wiki - User contributions [en]2024-03-28T22:52:22ZUser contributionsMediaWiki 1.35.1https://wiki.galenhealthcare.com/index.php?title=ECalcs_-_Integrated_Health_Calculators&diff=23369ECalcs - Integrated Health Calculators2021-10-22T16:03:09Z<p>Justin.Campbell: </p>
<hr />
<div>{{lowercase title}}<br />
<br />
{| {{table}} align="center" width="75%" cellpadding="10"<br />
| align="center" width="300" cellpadding="10" style="background:#f0f0f0;font-size:16pt;"|'''Integrated'''<br />
| align="center" width="300" cellpadding="10" style="background:#f0f0f0;font-size:16pt;"|'''Patient Specific'''<br />
| align="center" width="300" cellpadding="10" style="background:#f0f0f0;font-size:16pt;"|'''Documented'''<br />
|-<br />
| eCalcs is fully integrated into the Allscripts TouchWorks (formally Enterprise) EHR, eliminating the need to keep a list of links to outside health calculators and saving precious time with patients.<br />
||The current patient’s health information is pre-loaded into the calculator, reducing the time and errors in entering the clinical indicators for the calculator.<br />
<br />
||With the score in hand, we can also seamlessly document this in the patient’s EHR chart.<br />
<br />
<br />
|-<br />
| <br />
|}<br />
<br />
[[Image:eCalcs - sample screen.png|center]]<br />
<br />
<br />
<table align="center" border="0" cellpadding="10"><tr><td bgcolor="#ededed"><br />
'''[http://www.youtube.com/watch?v=46FgTlI9qbk&feature=player_embedded Introduction to eCalcs - 55s]''' </td><td bgcolor="#ededed"><br />
'''[http://www.youtube.com/watch?v=Pku7kB1rrrU&feature=player_embedded How to use eCalcs - 2m45s]'''</td><td bgcolor="#ededed"><br />
'''[http://www.youtube.com/watch?v=p5Xr9-F3SGA&feature=player_embedded Configuring eCalcs]'''</td></tr><tr><td align="center"><br />
[http://content.galenhealthcare.com/eCalcs/videos/eCalcs%20-%20Integrated%20Health%20Calculators.mp4 download the video]</td><td align="center"><br />
[http://content.galenhealthcare.com/eCalcs/videos/How%20to%20use%20eCalcs.mp4 download the video]</td><td align="center"><br />
[http://content.galenhealthcare.com/eCalcs/videos/eCalcs%20-%20Configuration.mp4 download the video]<br />
</td></tr></table><br />
<br />
<br />
<br />
<table border="0" bgcolor="#ededed"><tr><td>[http://www.galenhealthcare.com/products-services/products/ecalcs/ Read more about eCalcs or Request a Demo]</td></tr></table><br />
<br />
<br />
== Common Questions ==<br />
{| {{table}}<br />
| '''Which calculators are available?'''<br />
|-<br />
| Galen offers dozens of calculators, including the most popular ones like the Framingham Cardiac Risk, Breast Cancer Risk, CHADS2 for Risk of Stroke, ADA Diabetes Risk, MELD Score for Liver Disease. For a full list, see the list of [[ECalcs - Integrated Health Calculators#Available Calculators|Available Calculators]] below.<br />
| <br />
|-<br />
| '''Is it configurable?'''<br />
|-<br />
| Yes, the calculators are configurable and many are available from Galen. The chart data used for each measure is also configurable via a web-based management screen built into TWAdmin.<br />
|-<br />
| <br />
|-<br />
| '''How are scores documented?'''<br />
|-<br />
| Scores are documented as Results within the patient chart based on the Resultables setup to document the results of each calculator. Results may be shown in a flow sheet and auto-cited into a Note.<br />
|-<br />
|'''Can I cite the score into the Note?'''<br />
|-<br />
| Yes. The Result that is added to the patient’s chart may be cited into the current Note, and auto-cited into new Notes.<br />
|-<br />
| <br />
|-<br />
| '''Is eCalcs supported by Allscripts?'''<br />
|-<br />
| Galen fully supports eCalcs in your Allscripts environment. eCalcs utilizes standard components within Allscripts like the Web Framework and the standard Interface APIs.<br />
|-<br />
| <br />
|-<br />
| '''What software or controls are required?'''<br />
|-<br />
| None - eCalcs is fully integrated into Allscripts. No new ActiveX controls or other software is required on PCs using eCalcs within the Allscripts TouchWorks EHR.<br />
|-<br />
| <br />
|-<br />
| '''What new hardware is required?'''<br />
|-<br />
| No new server or PC hardware is required.<br />
|-<br />
| <br />
|-<br />
| '''Is Citrix supported?'''<br />
|-<br />
| Yes, eCalcs fully supports Citrix.<br />
|-<br />
| <br />
|-<br />
| '''Does eCalcs have an impact on the EHR?'''<br />
|-<br />
| There is no impact on the EHR in terms of performance or other negative consequences. Loading the eCalcs page is lightweight, requiring fewer web page and database calls than most screens in the EHR.<br />
|-<br />
| <br />
|-<br />
| '''How does eCalcs support upgrades to the EHR?'''<br />
|-<br />
| eCalcs is designed to be minimally impacted by any changes in the EHR system. Upgrades and migrations may require eCalcs components to be re-applied, though rarely will any configuration or software changes be required with a new version of Allscripts. In these cases, Galen will support the new version as part of the normal eCalcs maintenance package.<br />
|-<br />
| <br />
|-<br />
| '''When updates to the algorithms for calculators are made, is eCalcs updated?'''<br />
|-<br />
| Yes, the eCalcs maintenance package covers this. eCalcs calculators are updated along with changes in the medical research that support the online calculators.<br />
|-<br />
| <br />
|}<br />
<br />
==Implementation Details==<br />
'''Galen'''<br />
*Our EHR technicians will install the web server and database server components.<br />
*Training on configuration of eCalcs to client.<br />
<br />
'''Client – EHR Analyst'''<br />
*Training from Galen on configuration of eCalcs - about one hour.<br />
*Configure each calculator’s inputs, e.g. mapping which resultables should be considered the Total Cholesterol input for the Framingham Risk calculator – typically less than one hour per calculator.<br />
*Optional: add Orderable and Resultable Item Dictionary entries used to store the eCalcs. Clients typically have Galen deliver these entries by default using SSMT, which saves our clients the hour of setup this normally requires in TWAdmin.<br />
<br />
'''Client Resources'''<br />
* Server technician – provide access to the appropriate EHR servers – 1 hour.<br />
* EHR analyst – person familiar with the EHR build and dictionaries to configure the inputs on each calculator. See above for effort, approximately 2 hours plus 1 x number of calculators.<br />
* Clinical advisor – nurse, mid-level or provider to answer any clinical questions from the EHR analyst during setup.<br />
<br />
==Available Calculators==<br />
'''Currently Available'''<br />
<br />
* [[Galen eCalcs - Calculator: ADA Diabetes Risk (2013 Update)|ADA Diabetes Risk Calculator]]<br />
* [[Galen eCalcs - Calculator: Annual Health Assessment|Annual Health Assessment]]<br />
* [[Galen eCalcs - Module: Anticoag Module|Anticoag Module]]<br />
* [[Galen eCalcs - Calculator: ARIC Coronary Heart Disease Risk|ARIC Coronary Heart Disease Risk]]<br />
* [[Galen eCalcs - Calculator: CV Risk|ASCVD Risk Estimator Plus]]<br />
* [[Galen eCalcs - Calculator: International Prostate Symptom Score (IPSS)|International Prostate Symptom Score (IPSS) (previously AUA Symptom Score)]]<br />
* [[Galen eCalcs - Calculator: Bariatric Surgery|Bariatric Surgery]]<br />
* [[Galen eCalcs - Calculator: Bath Ankylosing Spondylitis Disease Activity Index (BASDAI)|Bath Ankylosing Spondylitis Disease Activity Index (BASDAI)]]<br />
* [[Galen eCalcs - Calculator: Body Surface Area|Body Surface Area]]<br />
* [[Galen eCalcs - Calculator: Breast Cancer Risk|Breast Cancer Risk]]<br />
* [[Galen eCalcs - Calculator: CAGE Alcohol Screening|CAGE Alcohol Screening]]<br />
* [[Galen eCalcs - Calculator: Caloric Requirements|Caloric Requirements]]<br />
* [[Galen eCalcs - Calculator: CEAP Classification for Chronic Venous Disorders|CEAP Classification for Chronic Venous Disorders]]<br />
* [[Galen eCalcs - Calculator: CHA2DS2-VASc for Risk of Stroke|CHA2DS2 - VASc for Risk of Stroke]]<br />
* [[Galen eCalcs - Calculator: CHADS2 for Risk of Stroke|CHADS2 for Risk of Stroke]]<br />
* [[Galen eCalcs - Calculator: Child-Pugh Score|Child-Pugh Score]]<br />
* [[Galen eCalcs - Calculator: Clinical COPD Questionnaire|Clinical COPD Questionnaire]]<br />
* [[Galen eCalcs - Calculator: Corrected QT Interval|Corrected QT Interval]]<br />
* [[Galen eCalcs - Calculator: Corrected Serum Calcium for Albumin|Corrected Serum Calcium for Albumin]]<br />
* [[Galen eCalcs - Calculator: CRAFFT Screening Questions|CRAFFT Screening Questions)]]<br />
* [[Galen eCalcs - Calculator: Creatinine Clearance|Creatinine Clearance]]<br />
* [[Galen eCalcs - Calculator: Creatinine Clearance (MDRD)|eGFR Calculators: MDRD Study and CKD-EPI Creatinine Equations]]<br />
* [[Galen eCalcs - Calculator: Crohn%27s Activity Index|Crohn's Activity Index]]<br />
* [[Galen eCalcs - Calculator: DASS21 (Depression/Anxiety/Stress)|DASS21 (Depression/Anxiety/Stress)]]<br />
* [[Galen eCalcs - Calculator: D.I.R.E Score|DIRE Score]]<br />
* [[Galen eCalcs - Calculator: DAS28|Disease Activity Score (DAS28) for Rheumatoid Arthritis]]<br />
* [[Galen eCalcs - Calculator: Duke Treadmill Score|Duke Treadmill Score]]<br />
* [[Galen eCalcs - Calculator: Edinburgh Postnatal Depression Scale|Edinburgh Postnatal Depression Scale (EPDS)]]<br />
* [[Galen eCalcs - Calculator: Edmonton Symptom Assessment Scale (ESAS)|Edmonton Symptom Assessment Scale (ESAS)]]<br />
* [[Galen eCalcs - Calculator: Epworth Sleepiness Scale|Epworth Sleepiness Study]]<br />
* [[Galen eCalcs - Calculator: Falls Risk Assessment|Falls Risk Assessment]]<br />
* [[Galen eCalcs - Calculator: Final Parental Height (FPH) Child Height Prediction|Final Parental Height (FPH) Child Height Prediction]]<br />
* [[Galen eCalcs - Calculator: Framingham Risk (2015)|Framingham Risk (2015)]]<br />
* [[Galen eCalcs - Calculator: Framingham Risk for General CVD|Framingham Risk for General CVD]]<br />
* [[Galen eCalcs - Calculator: Framingham Risk for Heart Attack|Framingham Risk for Heart Attack]]<br />
* [[Galen eCalcs - Calculator: Framingham Stroke Risk|Framingham Stroke Risk]]<br />
* [[Galen eCalcs - Calculator: FRAX WHO Fracture Risk|FRAX WHO Fracture Risk]]<br />
* [[Galen eCalcs - Calculator: Free|Free Bioavailable and Testosterone]]<br />
* [[Galen eCalcs - Calculator: GAD-7 Gen. Anxiety Disorder|GAD-7 General Anxiety Disorder]]<br />
* [[Galen eCalcs - Calculator: GRACE ACS Risk|GRACE ACS Risk]]<br />
* [[Galen eCalcs - Calculator: Growth Velocity|Growth Velocity]]<br />
* [[Galen eCalcs - Calculator: Gupta Perioperative Risk|Gupta Perioperative Cardiac Risk]]<br />
* [[Galen eCalcs - Calculator: Has Bled|HAS-BLED Score]]<br />
* [[Galen eCalcs - Calculator: HbA1c To Glucose Converter|HbA1c to Glucose Converter]]<br />
* [[Galen eCalcs - Calculator: Ideal Body Weight (All Ages)|Ideal Body Weight (All Ages)]]<br />
* [[Galen eCalcs - Calculator: Ideal Body Weight (Hamwi)|Ideal Body Weight (Hamwi)]]<br />
* [[Galen eCalcs - Calculator: IPSS|IPSS-R / IPSS-RA Calculator]]<br />
* [[Galen eCalcs - Calculator: Knee Society Score|Knee Society Score]]<br />
* [[Galen eCalcs - Calculator: LACE Index Scoring Tool|LACE Index Scoring Tool]]<br />
* [[Galen eCalcs - Calculator: Lung Cancer Screening Recommendation|Lung Cancer Screening Recommendation]]<br />
* [[Galen eCalcs - Calculator: M-CHAT|M-CHAT-R]]<br />
* [[Galen eCalcs - Calculator: Medication Adherence Rating Scale|Medication Adherence Rating Scale (MARS)]]<br />
* [[Galen eCalcs - Calculator: MELD Score for Liver Disease|MELD Score for Liver Disease]]<br />
* [[Galen eCalcs - Calculator: MELD Score for Liver Disease (w/ Na)|MELD Score for Liver Diease (w/ NA)]]<br />
* [[Galen eCalcs - Calculator: Modified LACE Index Tool|Modified LACE Index Tool]]<br />
* [[Galen eCalcs - Calculator: Mood Disorder Questionnaire|Mood Disorder Questionnaire]]<br />
* [[Galen eCalcs - Calculator: Narcotic Equivalency Converter|Opioid Equivalency]]<br />
* [[Galen eCalcs - Calculator: Newborn Weight Loss Percentage |Newborn Weight Loss Percentage]]<br />
* [[Galen eCalcs - Calculator: Opioid Morphine Equivalent Dose Calculator|Morphine Equivalent Dose Calculator]]<br />
* [[Galen eCalcs - Calculator: Opioid Risk Tool|Opioid Risk Tool]]<br />
* [[Galen eCalcs - Calculator: Oswestry Disability Index (ODI)|Oswestry Disability Index (ODI)]]<br />
* [[Galen eCalcs - Calculator: Pediatric Blood Pressure Percentile|Pediatric Blood Pressure Percentile]]<br />
* [[Galen eCalcs - Calculator: Pediatric BMI-for-Age Z-Score Calculator|Pediatric BMI-for-Age Z-Score Calculator]]<br />
* [[Galen eCalcs - Calculator: Pediatric Crohn’s Disease Activity Index (PCDAI)|Pediatric Crohn's Disease Activity Index (PCDAI)]]<br />
* [[Galen eCalcs - Calculator: Pediatric Symptom Checklist (PSC)|Pediatric Symptom Checklist (PSC)]]<br />
* [[Galen eCalcs - Calculator: PHQ 2014 (Depression Screening)|PHQ-2/9 (Depression Screening)]]<br />
* [[Galen eCalcs - Calculator: PHQ - A (PHQ-9 for Adolescents)|PHQ - A (PHQ-9 for Adolescents)]]<br />
* [[Galen eCalcs - Calculator: Pneumonia Severity Index|Pneumonia Severity Index]]<br />
* [[Galen eCalcs - Calculator: Post Concussion Symptom Scale|Post-Concussion Symptom Scale]]<br />
* [[Galen eCalcs - Calculator: Predicted Peak Flow|Predicted Peak Flow]]<br />
* [[Galen eCalcs - Calculator: Pregnancy Due Dates|Pregnancy Due Dates]]<br />
* [[Galen eCalcs - Calculator: Premature Baby Corrected Age|Premature Baby Corrected Age]]<br />
* [[Galen eCalcs - Calculator: PRIME-MD Depression Screening|PRIME-MD Depression Screening]]<br />
* [[Galen eCalcs - Calculator: QFracture Risk (QFRAX)|QFracture Risk (QFRAX)]]<br />
* [[Galen eCalcs - Calculator: RAPID3|RAPID3]]<br />
* [[Galen eCalcs - Calculator: Reynolds Risk Score|Reynolds Risk Score]]<br />
* [[Galen eCalcs - Calculator: Revised Cardiac Risk|Revised Cardiac Risk Index for Perioperative Cardiac Complications (Lee Index)]]<br />
* [[Galen eCalcs - Calculator: Rheumatoid Arthritis Clinical Disease Activity Index|Rheumatoid Arthritis Clinical Disease Activity Index (CDAI)]]<br />
* [[Galen eCalcs - Calculator: Risk Stratification Scoring|Risk Stratification Scoring]]<br />
* [[Galen eCalcs - Calculator: S2BI Oregon - Adolescent Annual Questionnaire|S2BI Oregon - Adolescent Annual Questionnaire]]<br />
* [[Galen eCalcs - Calculator: SBIRT Screen|SBIRT Screen]]<br />
* [[Galen eCalcs - Calculator: SBIRT Screening (Oregon)|SBIRT Screening (Oregon)]]<br />
* [[Galen eCalcs - Calculator: Simple Disease Activity Index (SDAI)|Simple Disease Activity Index (SDAI)]]<br />
* [[Galen eCalcs - Calculator: Six-Item Cognitive Impairment Test (6CIT)|Six-Item Cognitive Impairment Test (6CIT)]]<br />
* [[Galen eCalcs - Calculator: Smoking Pack Years Calculator|Smoking Pack Years Calculator]]<br />
* [[Galen eCalcs - Calculator: Social Determinants of Health Assessment|Social Determinants of Health Assessment]]<br />
* [[Galen eCalcs - Calculator: STOP BANG Questionnaire|STOP-Bang Questionnaire]]<br />
* [[Galen eCalcs - Calculator: SLEDAI|Systemic Lupus Erythematosus Disease Activity Index (SLEDAI)]]<br />
* [[Galen eCalcs - Calculator: STEADI|Extended Falls Risk Screening (STEADI)]]<br />
* [[Galen eCalcs - Calculator: Tobacco Screening|Tobacco Screening]]<br />
* [[Galen eCalcs - Calculator: Tufts DPP Risk Estimator|Tufts DPP Risk Estimator]]<br />
* [[Galen eCalcs - Calculator: Venous Severity Scoring (VSS)|Venous Severity Scoring (VSS)]]<br />
* [[Galen eCalcs - Calculator: Vulnerable Elders Survey (VES-13)|Vulnerable Elders Survey (VES-13)]]<br />
* [[Galen eCalcs - Calculator: Wells Score (DVT Risk)|Wells Score (DVT Risk)]]<br />
* [[Galen eCalcs - Calculator: Wound Calculator|Wound Care Management]]<br />
<br />
==General Configuration Options==<br />
<br />
<br />
===Description===<br />
In addition to the calculator specific configuration options the eCalcs solution also offers a list a global configuration options than can be set and applied the solution. These configuration options are located in TWAdmin - eCalcs Config - expand the top gear option named "Miscellaneous Configuration" to show the list of settings.<br />
<br />
<br />
===Miscellaneous Configuration Options===<br />
{| class ="wikitable"<br />
! style="background:#d0e5f5" | Name<br />
! style="background:#d0e5f5" | Description<br />
! style="background:#d0e5f5" | Settings<br />
|-valign ="TOP"<br />
<br />
|Accession Number Prefix || The prefix for note output accession numbers generated by eCalcs. || '''''G-MCF (default)''''' - can apply any alpha-numeric prefix to be filed as a prefix on document accession numbers.<br />
|-<br />
|Auto Calculate || When a calculator has all data it needs to calculate the result, and there are no inputs that are no populated by chart data, the calculator can automatically display the results without forcing the user to explicitly click the calculate button. || '''''True (default)''''' - calculators will automatically perform the calculation preview when minimum required information is met. <br><br> '''False''' - the user will be required to click Calculate in order to generate a calculation preview.<br />
|-<br />
|Default Abnormal Value Code || Various eCalcs offerings have support for submitting eCalcs results as being considered as abnormal. This setting enables the mapping of the TouchWorks abnormal codes to the calculator output. || '''''A (default)''''' - when an abnormal result is generated as defined by the calculator the eCalcs will file to the chart in an abnormal status (a red beaker). <br><br> '''NULL''' - there is no abnormal code available and the eCalcs configuration and the eCalcs will file into the chart as normal.<br />
|-<br />
|Default Encounter Type || Sets the code value for the encounter type to use when attempting to Add to Chart without an encounter already in context. || '''''3 - Other (default)''''' - valid values are code values from the Encounter Type dictionary.<br />
|-<br />
|Default Ethnicity Entry To Blank || Indicates whether or not the ethnicity inputs on calculators should default to blank. || '''True''' - global ethnicity mappings are not enabled or recognized and will require the ethnicity to be manually set in order to perform calculations where applicable. <br><br> '''''False (default)''''' - global ethnicity mappings are enabled and recognized for all calculators utilizing ethnicity as an input.<br />
|-<br />
|Default Provider Code || The entry code for the provider to use when using Add to Chart and there is no encounter provider currently in context. || '''''1TW090 (default)''''' - valid values are code values from the Provider or TWUser/Provider TouchWorks entries.<br />
|-<br />
|Default Race Entry To Blank || Indicates whether or not the race inputs on calculator should default to blank. || '''True''' - global race mappings are not enabled or recognized and will require the race to be manually set in order to perform calculations where applicable. <br><br> '''''False (default)''''' - global race mappings are enabled and recognized for all calculators utilizing race as an input.<br />
|-<br />
|Ethnicity Caucasian Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Caucasian code values for any calculator utilizing an ethnicity input. || '''''blank (default)''''' - valid values are a comma separated list of TouchWorks Caucasian code values for this ethnicity type.<br />
|-<br />
|Ethnicity Declined Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Declined code values for any calculator utilizing an ethnicity input. || '''''Declined (default)''''' - valid values are a comma separated list of TouchWorks Declined code values for this ethnicity type.<br />
|-<br />
|Ethnicity Hispanic Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Hispanic code values for any calculator utilizing an ethnicity input. || '''''Hispanic (default)''''' - valid values are a comma separated list of TouchWorks Hispanic code values for this ethnicity type.<br />
|-<br />
|Ethnicity Non Hispanic Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Non Hispanic code values for any calculator utilizing an ethnicity input. || '''''NonHispan,NotHispan (default)''''' - valid values are a comma separated list of TouchWorks Non Hispanic code values for this ethnicity type.<br />
|-<br />
|Ethnicity Not Reported Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Not Reported code values for any calculator utilizing an ethnicity input. || '''''NotReport (default)''''' - valid values are a comma separated list of TouchWorks Not Reported code values for this ethnicity type.<br />
|-<br />
||Ethnicity Unknown Mapping Codes || A comma-separated input list of codes that references the TouchWorks Ethnicity dictionary, used for supporting one or many valid Unknown code values for any calculator utilizing an ethnicity input. || '''''Unknown (default)''''' - valid values are a comma separated list of TouchWorks Unknown code values for this ethnicity type.<br />
|-<br />
||Filter And Favorites Threshold || When the number of installed calculators equals or surpasses this number, the searching and favorites features will become enabled. || '''''10 (default)''''' - valid values are 0 - max installed calculators.<br />
|-<br />
|Interface Source Id || The interface source ID to use when using Add to Chart. || '''''623 (default)''''' - valid values are numeric/integer values.<br />
|-<br />
|Maximum Mapper Items || Sets the maximum number of results to display in mapper controls. || '''''200 (default)''''' - valid values are numeric/integers that will update the results return threshold in eCalcs config input mappings.<br />
|-<br />
|Orderable Item Mapping || Sets the Orderable Item (QO_Classification_DE) entry code to use when filing calculator results into a patients chart if no calculator specific orderable item override values are set. || '''''G-eCalcs (default)''''' - valid values are code values from the TouchWorks Orderable Item dictionary. To properly utilize this option the referenced Orderable Item must be linked with ALL eCalcs result items.<br />
|-<br />
|Ordering Provider Drop Down Is Upper || This configuration option controls the location of the Ordering Provider drop down list on calculator screens. || '''''False (default)''''' - the Ordering Provider drop down list displays at the bottom of the eCalcs page. <br><br> '''True''' - the Ordering Provider drop down list displays at the top of the eCalcs page.<br />
|-<br />
|Ordering Provider Dropdown Use PCP For Non Provider User || This configuration option provides a configuration option that allows PCP entries to populate the Ordering Provider drop-down in eCalcs. || '''''False (default)''''' - the Ordering Provider drop-down is not populated with PCP values when the user is a non-provider user. <br><br> '''True''' - the patient PCP is used to populate the Ordering Provider drop-down when the user is a non-provider user.<br />
|-<br />
|Ordering Provider Label Text || This configuration option allows a custom label to be set for the Order Provider (default value) drop-down list in eCalcs. For example "Provider:" or "Caregiver:".<br />
|-<br />
|Race Asian Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Asian code values for any calculator utilizing a race input. || '''''AsianorPac,AO,Chinese,Japanese,Korean,Vietnamese (default)''''' - valid values are a comma separated list of TouchWorks Asian code values for this race type.<br />
|-<br />
|Race Black Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Black code values for any calculator utilizing a race input. || '''''Black (default)''''' - valid values are a comma separated list of TouchWorks Unknown code values for this ethnicity type.<br />
|-<br />
|Race Declined Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Declined code values for any calculator utilizing a race input. || '''''Declined (default)''''' - valid values are a comma separated list of TouchWorks Declined code values for this race type.<br />
|-<br />
|Race Hispanic Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Hispanic code values for any calculator utilizing a race input. || '''''Hispanic (default)''''' - valid values are a comma separated list of TouchWorks Hispanic code values for this race type.<br />
|-<br />
|Race Native American Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Native American code values for any calculator utilizing a race input. || '''''AmericanIn (default)''''' - valid values are a comma separated list of TouchWorks Native American code values for this race type.<br />
|-<br />
|Race Native Hawaiian or Pacific Islander Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Native Hawaiian Or Pacific Islander code values for any calculator utilizing a race input. || '''''Hawaiian,PIO,Palauan,Pohnpeian,Samoan,Marchalles,Guamanian (default)''''' - valid values are a comma separated list of TouchWorks Native Hawaiian or Pacific Islander code values for this race type.<br />
|-<br />
|Race Not Reported Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Race Not Reported code values for any calculator utilizing a race input. || '''''NotReport (default)''''' - valid values are a comma separated list of TouchWorks Not Reported code values for this race type.<br />
|-<br />
|Race Unknown Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid Unknown code values for any calculator utilizing a race input. || '''''Unknown (default)''''' - valid values are a comma separated list of TouchWorks Unknown code values for this race type.<br />
|-<br />
|Race White Mapping Codes || A comma-separated input list of codes that references the TouchWorks Race dictionary, used for supporting one or many valid White code values for any calculator utilizing a race input. || '''''Caucasian,White (default)''''' - valid values are a comma separated list of TouchWorks White code values for this race type.<br />
|-<br />
|Save Input Values || Indicates whether calculators should save the inputs used to generate results as an item level comment. || '''''True (default)''''' - input questions and answers are staged as item level comments in order to further support including these options at the calculator level. <br><br> '''False''' - input questions and answers are not staged as item level comments and enforced as discrete outputs with no item level comments.<br />
|-<br />
|Set Task Owner To Encounter Provider Always || Provides as option to always route an eCalcs task to the encounter provider in context. || '''''False (default)''''' - this behavior is not used and the behaviors associated with the preference Set Task Owner To Encounter Provider When User Not A Provider is applied. <br><br> '''True''' - generated tasks will use the provider encounter in context or the user-provider if doesn't exist.<br />
|-<br />
|Set Task Owner To Encounter Provider When User Not A Provider || For applicable calculator that utilize tasking this option can route eCalcs tasks to the Encounter Provider or to the Performing Provider. || '''''False (default)''''' - applicable to eCalcs that utilize tasking, any task generated will look to assign the task to the User/Provider or Provider that performed the calculation.<br><br> '''True''' - applicable to eCalcs that utilize tasking, any task generated will look to the Encounter Provider value to assign the task and not the User/Provider or Provider who performed it.<br />
|-<br />
|Show Unity Debugging || Indicates whether to show call-related debug information on calculator pages. || '''''False (default)''''' - Unity debugging to include call-related debug info is not available on calculator pages.<br><br> '''True''' - Unity debugging to include call-related debug info is available on calculator pages.<br />
|-<br />
|Units Pick List Name || Specifies the name of the units picklist assigned to eCalcs output resultable items and v10 units Note rendering. || '''''Health Calculator Units (default)''''' - valid values Unit Picklist Name entries that must contain the delivered and available unit values utilized for eCalcs; to support specifically v10 note rendering with regards to units.<br />
|-<br />
|Use Custom Ethnicity Mapping || Indicates whether or not the custom Ethnicity mappings in the global miscellaneous configuration will be enforced. || '''''True (default)''''' - enables the use of the Ethnicity specific eCalcs mapping inputs. <br><br> '''False''' - disables the use of the Ethnicity specific mapping inputs and falls back to force blank.<br />
|-<br />
|Use Custom Race Mapping || Indicates whether or not the custom Race mappings defined in the global miscellaneous configuration will be used. || '''''True default)''''' - enables the use of the Race specific eCalcs mapping inputs. <br><br> '''False''' - disables the use of the Race specific mapping inputs and falls back to force blank.<br />
|-<br />
|Use Ordering Provider Drop Down || Controls whether or not the Ordering Provider drop down list appears for use in the eCalcs module. || '''''True (default)''''' - the Ordering Provider drop down list is available for use. <br><br> '''False''' - the Ordering Provider drop down option is not available for use.<br />
|-<br />
|Use Unity || Sets whether to use Unity calls where available. || '''''False (default)''''' - disables the use of Unity calls.<br><br> '''True''' - enables the use of Unity calls.<br />
|-<br />
|Use WIP Data || Sets whether or not to look in WIP tables for patient data. || '''''True (default)''''' - enables the solution to look in WIP tables for patient data. <br><br> '''False''' - disables the solution from looking in WIP tables for patient data. <br />
|-<br />
|Verification Not Required For Providers || This determines whether or not a Provider requires verification on their eCalcs results. || '''''False (default)''''' - a user that is a Provider will not require results verification for applicable calculators when verification is enabled. <br><br> '''True''' - a user that is a Provider will require results verification for applicable calculators when verification is enabled.<br />
|-<br />
|Verification Required Flag || Sets the result verification behavior at the framework level in eCalcs. || '''''False (default)''''' - calculators configured to use verification will not generate a verification task. <br><br> '''True''' - calculators configured to use verification will generate a verification task.<br />
|-<br />
|Where Performed Code || The where performed entry code value set when Adding to Chart. || '''''1 - Other (default)''''' - valid values are code values from the TouchWorks Where Performed dictionary.<br />
|}<br />
<br />
==Downloads==<br />
An electronic copy of this page may be downloaded as a PDF: [[Media:Galen eCalcs Brochure.pdf|eCalcs Brochure]]<br />
<br />
==Articles==<br />
*[http://blog.allscripts.com/2013/06/19/open-app-spotlight-do-patients-know-what-those-numbers-mean/ Open App Spotlight: Do Patients know what those numbers mean?]<br />
*[http://blog.galenhealthcare.com/2014/11/08/ecalcs-new-release-v1-4-0/ eCalcs New Release (11/8/2014)]<br />
*[http://blog.galenhealthcare.com/2014/06/17/ecalcs-first-steps-towards-meaningful-use-compliance/ eCalcs: First steps towards meaningful use compliance]<br />
<br />
<br />
<br />
__toc__</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23029COVID-192020-03-19T19:29:01Z<p>Justin.Campbell: </p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]<br />
*[https://www.thisweekhealth.com/covid19/ This Week in Health IT COVID-19 Resources]<br />
*[https://www.covid19healthtech.com/ Health Tech Responds to COVID-19]<br />
*[https://www.healthcareitnews.com/news/key-resources-keep-track-coronavirus-pandemic Healthcare IT News Key Resources to Keep Track of the Coronavirus Pandemic]<br />
*[https://histalk2.com/2020/03/19/health-system-frontline-reports-and-tips-coronavirus-response/ HISTalk Health System Frontline Reports and Tips – Coronavirus Response]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23028COVID-192020-03-19T19:20:41Z<p>Justin.Campbell: /* Resources */</p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]<br />
*[https://www.thisweekhealth.com/covid19/ This Week in Health IT COVID-19 Resources]<br />
*[https://www.covid19healthtech.com/ Health Tech Responds to COVID-19]<br />
*[https://www.healthcareitnews.com/news/key-resources-keep-track-coronavirus-pandemic Healthcare IT News Key Resources to Keep Track of the Coronavirus Pandemic]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23027COVID-192020-03-19T19:19:22Z<p>Justin.Campbell: /* Resources */</p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]<br />
*[https://www.thisweekhealth.com/covid19/ This Week in Health IT COVID-19 Resources]<br />
*[https://www.covid19healthtech.com/ Health Tech Responds to COVID-19]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23026COVID-192020-03-19T19:17:51Z<p>Justin.Campbell: /* Resources */</p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]<br />
*[https://www.thisweekhealth.com/covid19/ This Week in Health IT COVID-19 Resources]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23025COVID-192020-03-19T19:17:32Z<p>Justin.Campbell: /* Resources */</p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]<br />
*[COVID-19 Resources for Health Systems This Week in Health IT COVID-19 Resources]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=COVID-19&diff=23024COVID-192020-03-19T19:16:50Z<p>Justin.Campbell: Created page with "=Resources= *[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]"</p>
<hr />
<div>=Resources=<br />
*[https://www.chilmarkresearch.com/covid-19-free-health-it-resources/ Chilmark Research COVID-19: Free Health IT Resources]</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=ConnectR_Interface_Troubleshooting&diff=22539ConnectR Interface Troubleshooting2018-08-03T14:48:15Z<p>Justin.Campbell: </p>
<hr />
<div>[[Category:ConnectR]]<br />
== Debug Procedure ==<br />
1. Ensure Error Message Definitions are loaded into ConnectR database. If Error Message Definitions are not loaded into ConnectR database there is a database script available to load.<br><br />
2. Copy command from Target Message Grid into SQL Query window<br><br />
3. Remove beginning and end parenthesis<br><br />
4. Edit/Find ‘ -> Replace with ‘’(single quote with double single quote)<br>Note that SQL does not process double quotation marks. Find '''Single Quotation Mark''' and replace with '''two Single Quotations Marks'''.<br />
[[Image:ConnectR_Debug_Documentation_Img6.jpg]]<br><br><br />
5. Insert a comma after the name of the stored procedure<br><br><br />
6. Add a single quote before the first value being passed to the stored procedure and add a single quote after the last value<br><br><br />
7. Run sp_idxgenspcall, sp_name (for example, FileApppointment_CMS), with the remaining SQLCommand encapsulated in single quotes (both at the beginning and end). Also, remember to insert a comma after the name of the stored procedure. Before you execute this query, make sure the results are set to 'Results to Text'.<br><br />
8. Us the sp_idxgenspcall query at the beginning of the text. <br><br />
9. Query Options / select Text under Results. <br><br />
10. Copy text results & paste into new query window<br><br />
[[Image:ConnectR_Debug_Documentation_Img7.jpg]]<br><br><br />
11. Add begin tran (at the beginning of the script) / rollback tran (to the end of the script) to query. Execute query and utilize this information to root cause the error.<br><br />
12. If 0 is not returned, then continue to query the stored procedure call by Highlight the Stored Procedure / Right Click Scripts Stored Procedure as / Create to / New Query Editor Window, this will allow you to review the call procedure and what the expected value is for each field, you can also search the call for the error codes.<br><br />
<br />
== Example ==<br />
In the example shown below, required fields were present in the Stored Procedure called by the mapping, but were not present in the current Interface mapping. Thus the outcome was that the target message had to be changed to include the additional fields.<br><br />
[[Image:ConnectR_Debug_Documentation_Img5.jpg]]<br><br><br />
<br />
== Hint ==<br />
Cycle systems after changing a mapping<br><br />
[[Image:ConnectR_Debug_Documentation_Img8.jpg]]<br><br><br />
<br />
== Notes ==<br />
If you are encountering SQL formatting, syntax, or other errors when trying to run the queries check the following:<br />
#There should be a comma after the name of the stored procedure. For example, the beginning of the query should read, "sp_idxgenspcall FileAppoinment_CMS,"<br />
#The text immediately following this comma should be enclosed in a single quotation, and the corresponding single closing quotation should be the last character input as part of the query.<br />
#Make sure the results of the query in step 5 are sent to text, as this information is needed for step #7.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=File:Galen_VCO_Data_Migration_in_Healthcare-FINAL_CRUG2017-03.1.pptx&diff=21710File:Galen VCO Data Migration in Healthcare-FINAL CRUG2017-03.1.pptx2017-03-08T14:32:07Z<p>Justin.Campbell: </p>
<hr />
<div></div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21560HIE Participant Onboarding Resources2016-09-12T20:28:03Z<p>Justin.Campbell: /* Notifications */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Documents==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. <br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is flagged.<br />
<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21559HIE Participant Onboarding Resources2016-09-12T20:27:16Z<p>Justin.Campbell: /* Document Tree */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Documents==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. <br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is flagged.<br />
<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21558HIE Participant Onboarding Resources2016-09-12T20:27:07Z<p>Justin.Campbell: /* Document Tree */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. <br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is flagged.<br />
<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21557HIE Participant Onboarding Resources2016-09-12T20:26:07Z<p>Justin.Campbell: /* Document Tree */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21556HIE Participant Onboarding Resources2016-09-12T20:25:36Z<p>Justin.Campbell: /* Access Levels - Roles and Groups */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21555HIE Participant Onboarding Resources2016-09-12T20:24:46Z<p>Justin.Campbell: /* Worklists */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21554HIE Participant Onboarding Resources2016-09-12T20:24:33Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br><br />
<br />
==Worklists==<br />
• Personal to the clinician who created the worklist<br />
• Patient names can be added to a worklist either from the results of a search, or from the Patient context bar</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21553HIE Participant Onboarding Resources2016-09-12T20:23:18Z<p>Justin.Campbell: /* User Messaging */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button.<br><br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br><br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button.<br></div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21552HIE Participant Onboarding Resources2016-09-12T20:21:57Z<p>Justin.Campbell: /* Results Viewer */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. <br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21551HIE Participant Onboarding Resources2016-09-12T20:21:15Z<p>Justin.Campbell: /* Results Viewer */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative view may displays a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21550HIE Participant Onboarding Resources2016-09-12T20:20:20Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies a sample user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable based upon the HIE vendor in use and are predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21549HIE Participant Onboarding Resources2016-09-12T20:19:44Z<p>Justin.Campbell: /* Administrator Homepage */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br><br><br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user.<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21548HIE Participant Onboarding Resources2016-09-12T20:19:16Z<p>Justin.Campbell: /* Administrator Homepage */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
Clinician Homepage<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21547HIE Participant Onboarding Resources2016-09-12T20:18:54Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
Clinician Homepage==<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
==User Messaging==<br />
Portal users will be able to send messages to and receive messages from other Portal users via the Portal’s User Messaging. Notifications will also arrive as a user message within the Portal.<br />
• Filtering Received Messages by selecting one or more of the options from the navigation bar:<br />
• Urgent Messages: Allows a user to view all urgent messages<br />
• Unread Messages: Allows a user to view all messages that have not been read<br />
• User Messages: Allows a user to view all messages sent by other Clinical Portal users<br />
• System Messages: Allows a user to view all messages sent by the Administrator<br />
• Reset: Allows the user to reset the filter criteria<br />
Users may also perform a text search to identify text in the message’s subject line. Users may enter the text and select the Search button. <br />
The following six columns appear on the Received Messages screen: Icons: The icon indicates an unread message. The icon indicates a read message. The icon indicates an attachment is included in the message.<br />
• From: Provides the name of the Clinical Portal user who sent the message. Note: Users may sort this column by clicking the From link.<br />
• Subject: Displays the subject line of the message. Note: Users may sort this column by clicking the Subject link.<br />
• ID: Shows the identification of the patient e.g. name or MRN. Note: Users may sort this column by clicking the ID link.<br />
• Event: Indicates the type of event e.g. blood test, scan etc. Note: Users may sort this column by clicking the Event link.<br />
• Received: Displays the date the email was received. Note: Users may sort this column by clicking the Received link.<br />
From this screen, a user may also delete a message that is no longer required, or send a new message to a Clinical Portal user. <br />
When the message is selected, the user may reply to the received message, forward the received message, print the received message and/or mark the message as unread.<br />
New Messages - Users may send new messages to other Clinical Portal users. The recipient's User ID can be typed directly into the To: field or, by clicking the To: button. A recipient can be identified from the resulting User Search screen.<br />
Sent Messages - Users may view messages they have sent to other Clinical Portal users.<br />
Deleting a Message - A message can be deleted by selecting its associated checkbox and clicking the Delete button. Deleting a message must be confirmed and cannot be undone.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21546HIE Participant Onboarding Resources2016-09-12T20:17:47Z<p>Justin.Campbell: /* Results Viewer */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
Clinician Homepage==<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21545HIE Participant Onboarding Resources2016-09-12T20:17:33Z<p>Justin.Campbell: /* Results Viewer */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
Clinician Homepage==<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br><br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21544HIE Participant Onboarding Resources2016-09-12T20:17:10Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
==Access Levels - Roles and Groups==<br />
The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
==Administrator Homepage==<br />
Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
Clinician Homepage==<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
==Document Tree==<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
==Frontdesk==<br />
Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
==Notifications==<br />
The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
==Patient Lists==<br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
==Patient Search==<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
==Patient Summary==<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
==Results Viewer==<br />
'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21543HIE Participant Onboarding Resources2016-09-12T20:14:11Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|-<br />
|Patient Summary ||<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
|-<br />
|Results Viewer||'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br />
<br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21542HIE Participant Onboarding Resources2016-09-12T20:13:51Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|-<br />
|Patient Summary ||<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
|-<br />
|Results Viewer||'''Textual Results'''<br />
The Results panel displays the text of the report and includes report's Status: Interim, Final or Updated<br />
Each result contains the following data in the header:<br />
• Time Collected – date/time the investigation was requested <br />
• Time Received – date/time the request was received <br />
• Time Reported – date/time the report was returned to the hospital <br />
• Order Number - the unique order number associated with the report <br />
• Ordering Provider -name of clinician who requested the investigation <br />
• Placer Notes - identifier associated with request when it was received <br />
• Filler Notes -identifier associated with the request when it was filled <br />
'''Numerical Results'''<br />
Each result contains the following data in the header:<br />
• Latest Version <br />
• Source System - (or other text) identifies the name of the source system <br />
• Time Collected – date/time the test specimen was collected <br />
• Time Received - date/time the test specimen was received by the laboratory <br />
• Time Reported - date/time the results were returned to the hospital <br />
• Order Number - the unique order number associated with the test <br />
• Status - the status of the results (Updated, Final, Interim) <br />
• Location - (optional) the location where the test was performed <br />
Cumulative Views - The same laboratory test may be requested for a patient a number of times during the course of their treatment. The Cumulative screen displays, for example, a table of results in age order, with the current <br />
result displayed with a colored background<br />
Charting - A Chart can be generated to reveal any trends or patterns that may be present in the results. Individual values are selected for inclusion in the chart by clicking their corresponding checkboxes.<br />
'''Microbiology Results'''<br />
The main report message contains the header information and usually provides an update with the micro-organisms found in the specimen. Each of the child report messages contains the full information for a particular organism. The main report message and children report messages are linked together to provide the complete micro-biology report. Cumulative views and charting are not applicable to microbiology. Some microbiology results are received in textual format and in this case the Portal will simply display the report.<br />
Abnormality flag identifies test values outside the reference range. An associated description will be displayed in red: for example Above upper panic limits. The HIE Clinical Portal does not determine whether or not this flag is displayed; this is determined from the contents of the message returned by the laboratory<br />
Data normalization is achieved using Health Language’s Language Engine (LE). Lab results presented in the results viewer will be normalized using the LOINC content set, allowing a cumulative view and charting across multiple source systems.<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21541HIE Participant Onboarding Resources2016-09-12T20:08:57Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|-<br />
|Patient Summary ||<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21540HIE Participant Onboarding Resources2016-09-12T20:08:40Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|-<br />
|Patient Summary ||<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in <br />
capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21539HIE Participant Onboarding Resources2016-09-12T20:08:22Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|-<br />
|Patient Summary ||<br />
• Patient Context Bar: Once a patient has been placed in context, their identification details are displayed in the Patient Context Bar. These include the patient's EMPI Identifier, Local MRNs, the patient's family name in capitals, followed by their first and other names, the patient's gender and date of birth, displayed in smaller text, and an indicator that the patient is deceased<br />
• Demographics: displays key demographic information for the patient including next of kin<br />
• Encounter History: displays a list of all inpatient and ED visits for the patient including Ambulatory<br />
• Medication History: displays a list of current and historic medications for the patient<br />
• Allergies: displays a list of current and historic allergies for the patient<br />
• Procedures: displays a list of procedures performed for the patient<br />
• Problems: displays a list of current and historic problems for the patient<br />
• Insurance: displays a list of latest insurance information from each contributing source.<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21538HIE Participant Onboarding Resources2016-09-12T20:06:47Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
| Patient Search ||<br />
• Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that that match the criteria within the HIE EMPI <br />
• Patient Demographic search results will display the EMPI identifier, EMR (Local) IDs, Name, Date of Birth (Age), Sex, Consent and Zip Code. A tooltip will display the address and phone number.<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21537HIE Participant Onboarding Resources2016-09-12T20:05:38Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the <br />
folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not <br />
been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red <br />
respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving <br />
the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual <br />
notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21536HIE Participant Onboarding Resources2016-09-12T20:04:28Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21535HIE Participant Onboarding Resources2016-09-12T20:04:02Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage ||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists<br />
• Favorite Searches <br />
• Search Results in Context<br />
• Recent Patients<br />
|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21534HIE Participant Onboarding Resources2016-09-12T20:03:23Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists<br />
• Favorite Searches <br />
• Search Results in Context<br />
• Recent Patients<br />
|| <br />
• Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21533HIE Participant Onboarding Resources2016-09-12T20:02:52Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists<br />
• Favorite Searches <br />
• Search Results in Context<br />
• Recent Patients<br />
|| • Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21532HIE Participant Onboarding Resources2016-09-12T20:01:58Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists<br />
• Favorite Searches <br />
• Search Results in Context<br />
• Recent Patients|| • Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21531HIE Participant Onboarding Resources2016-09-12T20:01:29Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
|-<br />
|Patient Lists<br />
• Favorite Searches <br />
• Search Results in Context<br />
• Recent Patients|| • Favorite Search is a saved set of criteria that can be recalled for later re-use by the logged in user. A favorite search is created by performing a search then entering a name for the criteria set into the Enter a new favorite search field<br />
• Search Results in Context the names returned by a search are held in memory when an individual is selected. This allows an alternative patient to be selected without having to repeat the search<br />
• Recent Patients list is automatically populated with the names of the 40 most recent patients as they are seen by the user. It is subdivided by how long ago the record was viewed; e.g. Today, Last 7 Days, Last 4 Weeks or Last 12 Months<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21530HIE Participant Onboarding Resources2016-09-12T19:59:02Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|-<br />
| Notifications||The following notifications are available as part of the SaaS Service<br />
• Inpatient Admission<br />
• Inpatient Discharge<br />
• New Laboratory Result (Final) is available<br />
• New Radiology Result (Final) is available<br />
• Interim Microbiology Result available<br />
• Patient is admitted to the ER<br />
<br />
Delivery Options for notifications are:<br />
Email – this will send a notification to the user via email that new information is available:<br />
• Individual Email: Sends the summary notification (without patient information) to the email address identified above. <br />
• Daily Summary Email: Sends a daily summary email (without patient information) of the notifications as opposed to individual notifications <br />
HIE Portal User Messaging (Individual): Sends the detailed notification containing patient information and selected document or result from the document tree securely to ‘Received Messages’ in HIE Portal. Note the user receiving the message needs to be an existing HIE Portal user<br />
Daily Summary HIE Portal User Messaging: Sends a daily summary of the notifications containing patient information and selected document or result securely to ‘Received Messages’ in HIE Portal as opposed to individual notification. Note the user receiving the message needs to be an existing HIE Portal user<br />
| <br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21529HIE Participant Onboarding Resources2016-09-12T19:56:16Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
|-<br />
| Frontdesk||Patient Search enables a clinician to find a patient or patients by searching on their personal details. A Patient search will return all patients that have been registered with the hospital or one of its facilities or clinics<br />
|<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21528HIE Participant Onboarding Resources2016-09-12T19:53:42Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|Document Tree<br />
Displays a categorized list of :<br />
• Laboratory<br />
• Radiology<br />
• Transcriptions<br />
||<br />
• Viewing Documents – Documents are stored in a hierarchy of folders in the document tree and can be filtered by the following metadata if available:<br />
o Category - document's type; e.g. X-ray or Chemistry <br />
o Date - document was either created or received from an external system such as a laboratory. When viewed by date, the folder names change to reflect the age of the documents they contain; e.g. Today, Last Week, Last Month <br />
o Service - lists the folders and documents by the service with which they are associated <br />
o Author - lists the folders and documents in ascending alphabetical sort order of the name of the clinician responsible for ordering or creating the document<br />
• Document Display Options - Folders and documents are listed in the document tree with the most recently created document appearing first. The number of documents in a folder is indicated by the bracketed numbers after the folder's title. The first number is the number of unread (by the current user) documents in the folder; the second is the total number of documents, both read and unread. If there are any documents in the folder which have not been viewed, the folder's title will be displayed in bold<br />
• Abnormal and Critical Abnormal Values - When a numerical result is returned from a laboratory that contains abnormal or critically abnormal values, that result's entry in the document tree is colored orange or red respectively. Other values for outstanding Abnormal and Critical Abnormal can be displayed, e.g. panic flags<br />
• Document Tool Tip - Each document listed in the document tree has an associated tooltip, which can be viewed by hovering the mouse pointer over the document's title<br />
• Look for Filter - Any text appearing in the tooltip can be entered into the Look For filter; this action immediately restricts the documents listed in the tree to only those which have the matching text in their tooltip<br />
| <br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21527HIE Participant Onboarding Resources2016-09-12T19:51:51Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21526HIE Participant Onboarding Resources2016-09-12T19:51:39Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
| <br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21525HIE Participant Onboarding Resources2016-09-12T19:51:27Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
| Clinician Homepage <br />
• Worklist<br />
• Recent Patients<br />
• Received Messages<br />
||<br />
• Worklist - identifies the worklist that will appear on the user's Homepage <br />
• Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
• Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
| <br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21524HIE Participant Onboarding Resources2016-09-12T19:48:58Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
|-<br />
| "Clinician Homepage <br />
|-<br />
| • Worklist<br />
|-<br />
| • Recent Patients<br />
|-<br />
| • Received Messages<br />
|-<br />
| <br />
|-<br />
| "||"• Worklist - identifies the worklist that will appear on the user's Homepage <br />
|-<br />
| • Recent Patients - a list of patient records that the user has recently accessed within the Portal<br />
|-<br />
| • Received Messages - a list of messages that the user has received from another user. This window will only display messages created within the Portal<br />
|-<br />
| "<br />
|-<br />
| <br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21523HIE Participant Onboarding Resources2016-09-12T19:48:28Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21522HIE Participant Onboarding Resources2016-09-12T19:48:11Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|-<br />
| Administrator Homepage ||• Clinical Portal Users Search enables an administrator to find users registered in the Clinical Portal<br />
|-<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21521HIE Participant Onboarding Resources2016-09-12T19:47:19Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br><br />
{| {{table}} border=1<br />
| align="center" style="background:#f0f0f0;"|'''Summary'''<br />
| align="center" style="background:#f0f0f0;"|'''Detail'''<br />
|-<br />
| Access Levels - Roles and Groups||The following roles and groups will be made available to manage privacy; additional roles and groups can be added and managed as necessary by an Administrator Function by HIE staff.<br />
• Front Desk <br />
• Care Support<br />
• Support<br />
• Provider <br />
• Facility Administrator<br />
• Facility Privacy Administrator<br />
• HIE Privacy Administrator<br />
• HIE Administrator <br />
• EMPI Administrator<br />
|}</div>Justin.Campbellhttps://wiki.galenhealthcare.com/index.php?title=HIE_Participant_Onboarding_Resources&diff=21520HIE Participant Onboarding Resources2016-09-12T19:39:22Z<p>Justin.Campbell: /* User Acceptance Criteria */</p>
<hr />
<div>=Documents & Artifacts=<br />
*[[:File:New_World_HIE_On-boarding_Readiness_Questionnaire_with_Addendum.docx|New World HIE On-Boarding Readiness Questionnaire]]<br />
*[[:File:New World HIE ADT Technical Design Document.docx| New World HIE ADT Technical Design Document]]<br />
*[[:File:New World HIE Sample CCDA Use Case.docx|New World HIE Sample CCDA Use Case]]<br />
<br />
=Lessons Learned=<br />
==Connectivity==<br />
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br><br />
*What type of connection will the participant be using?<br />
*VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant<br />
*How many VPNs can be completed concurrently?<br />
*How many dedicated connectivity resources will the HIE have dedicated?<br />
*Which participants are ready to engage at what time?<br />
*Does HIE have a schedule in terms of building these VPN connections?<br />
*VPN connectivity to all HIE environments: Test, Stage, Prod<br />
<br />
==Kick Off Meetings with Net New Participants==<br />
The following should be complete prior to kick off call if possible:<br><br />
*Will participants be receiving information from HIE (outbound to participant)?<br />
**If so, what specs do they need to receive for each message type they plan to receive?<br />
*What types of interfaces will the participant be connecting to HIE (inbound from participant)?<br />
*System code for facility added to system and portal<br />
*If participant is sending ORUs:<br />
**Are all results LOINC Coded?<br />
**Understanding how OBR-4/OBX-3 is sent<br />
**Ensure corrections, cancellations work as participant expects, etc…<br />
**Proper handling of sensitive lab information/do they send it?<br />
**If sending radiology, will they be participating in an Image Exchange?<br />
*Interface Analyst Contact Information<br />
**Phone/email<br />
*UAT Contacts (Validators)<br />
**Phone/email<br />
*Test plan for UAT from participant?<br />
**If not, we need one<br />
***ADT – event type flow, testing all event types<br />
***ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results<br />
***MDM – testing cancellations, corrections, etc…<br />
*Established timeline for go-live<br />
**Testing <br />
**UAT <br />
**Activation <br />
**Go-live issue resolution <br />
<br />
==Preparedness==<br />
*Inbound Feeds<br />
**Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production<br />
**Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient<br />
*Outbound Feeds<br />
**Understand how they function, where input facility specific logic needs to be input, etc…<br />
<br />
==Documentation of Standards==<br />
*Prefixes and Suffixes<br />
*PV1 Providers and Copy To Providers in OBR NTE Segments<br />
*OBX-3 is a copy of ‘OBR-4’ on RADs<br />
*Naming Conventions<br />
<br />
==User Acceptance Testing==<br />
*Ensure that aesthetic formats and HL7 standards are met<br />
**OBR-4/OBX-3<br />
**PV1 Providers in NTE segments<br />
**Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value<br />
*Follow Test Plans through each message type<br />
**Event types and message order <br />
**Cancellations and corrections<br />
**Microbiology messages and pathology messages<br />
**Sensitive Lab testing<br />
**Look for invalid characters<br />
*Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off<br />
**Standardized process for HIE Validation<br />
**Standardized process for Participant UAT Validation<br />
**Standardized process for migration through environments<br />
<br />
=User Acceptance Criteria=<br />
The table below identifies the user acceptance criteria to be used by the HIE during the User Acceptance Testing Process. These criteria are applicable predicated on the data provided by the HIE supporting the functionality. If data is lacking, functionality may not be possible.<br><br></div>Justin.Campbell