Deployment Planner. inexx Novo Grid Practice Agent HW Requirements.pdf

Transcription

1 Deployment Planner Introduction The purpose of this document is to collect information and configuration data necessary for implementation of the practice agent for electronic results delivery. Required fields are indicated by a red asterisk * Requested Connection Date If your practice will be interfacing results to an EMR, ensure the EMR vendor has the capacity to work in this timeframe before submitting this request. Please provide the quarter and year as the requested connection date. After evaluation, a Liaison will respond with an actual Kickoff date to initiate the connection. Current Date Requested Connection Date Deployment Lead Please provide Deployment Lead information and contact data as indicated below Name Phone Number Practice Resources Please provide Organization and Practice information (may be the same) and contact data as indicated below. If an organization has multiple practice locations, a practice planner will need to be completed for each location. *Organization Name *Practice Name Specialty/type # of Clinics Practice Address Street Street 2 City State Zip Clinical Contact: *Name *Phone *FAX Number * Technical Contact: Name Phone Practice Server Requirements The server hosting the Medicity Grid node software should be an always on system. Please access the link below for the most current hardware requirements inexx Novo Grid Practice Agent HW Requirements.pdf **Note: The node software requires HTTPS access to the internet over port 443. Only if a proxy server is leveraged for internet access at the practice, please provide the following detail: Proxy hostname: Proxy port: Proxy user ID: Proxy password:

2 Practice Provider Information Providers *Last Name *First Name *Title Hospital (Source) Practice (Destination) Middle (e.g. MD) *Provider NPI *Provider Code *Provider Code *Facility *Services Services Services Services

3 Practice Filter configuration The data requested below is used in configuring the results delivery and filtering characteristics for the practice. s Provided The following result types will be available to practices. s Results Delivery Methodology There are 3 options that a practice can select to receive results. After reviewing the options Deliver Method (EMR, inexx) Note: ADT messages often not desired to be delivered via interface due to demographic inexx Delivery The DropBox delivery solution delivers configured result types to a web browser interface.

4 E.2.1 Document Naming The following are the data elements used in constructing the output file name. Example: C:\LAB\SMITH, JOHN~MILES~REBECCA~ANN~F~Jun 5, 1934~ ~ ~ pdf *Lab Reports Interested Provider Last Name First Name Middle Name Gender DOB SSN Internal Number Accession Number *Textual Reports Interested Provider Last Name First Name Middle Name Gender DOB SSN Internal Number Accession Number Test/Report Name E.2.2 Document Delivery Locations List the names of the folders (local or network accessible file shares) into which the system will deposit the generated result documents: *Folder (include full local path or UNC path) N/A **Note: remote shares on the network must have appropriate rights granted (read/write/delete) so that the Novo agent service can create and manage files. Rights must be granted to the account executing the Novo Grid Platform service.

5 EMR HL7 Interface Configuration Data *EMR Vendor/Type *Contact Name *Phone * Choose from one of the following two methods of HL7 message transmission. Note that many EMR vendors require separate interfaces for lab results and reports. Please contact the EMR vendor for further information. TCP/IP interface For TCP/IP based transmission of results, list the IP and port addresses of the EMR interfaces: IP Port File-based interface For file based HL7 transmission, list the names of the folders (network accessible file shares) the EMR will poll for incoming results: Folder If applicable, list the names of the folders the EMR will deposit acknowledgements: Folder Results Reconciliation **Note: As results are delivered to an EMR interface, matching is done based on a configurable set of options (typically doctor, patient name, date of birth, and gender). If a patient or doctor match is not found, it will be necessary to fully understand the reconciliation process of the particular EMR. Please investigate this process prior to start of the test effort associate with the results delivery implementation.