ehnlogo

In order to qualify for Financial Incentives under the ARRA/HITECH Act "Meaningful Use" provision, eligible providers must have an ONC Certified EHR, ePrescribe, use CPOE, Share Data, Engage patients and Report to Public Health Agencies...
link Learn More

Hybrid Data Model

ehn

The MASH iNetwork is a Hybrid Data Model (HDM) that uses a clinical data repository for immediate access to patient protected health information (PHI) and federated data architecture, to logically separate data into “vaults” controlled by the organization that contributes the data in a highly secured virtual private network (VPN).  The architecture design consists of an IHE-based Health Information Exchange (HIE), Electronic Health Record (EHR) Integration and a community-based, Personal Health Record (PHR) with consumer applications and data analytics tools.  The MASH iNetwork provides fast, efficient, easy to use, safe and secure access to health information in real-time. 

    • Tiani-Spirit EHR Federated Data Architecture -Tiani-Spirit EHR is a secured, end-to-end, standards-based solution that enables patient-centric access to medical records. It enables interoperability and access to of patient data among multiple healthcare providers and locations. Tiani-Spirit EHR allows publishing, discovery and retrieval of patient information, including lab reports, imaging documents, physician notes and other data using Cisco UCS Express encrypted AXP Routers. It is a secured web portal that supports Secured Socket Layer (SSL) and Virtual Private Network (VPN) using web standards so authorized patients and providers have real-time access to health information on their PC’s and other devices. Tiani-Spirit EHR meets compliance with an Audit Trial Node Authentication (ATNA) framework for highly secured Protected Health Information (PHI).
    • MedStore Clinical Data Repository (CDR) - Once patient records are found, the Clinical Data Repository (CDR) collect, organize and aggregate clinical data from multiple sources. The consolidated clinical data is easily viewed and queried seamlessly to restricted healthcare providers. Incoming data streams can be further transformed, filtered and delivered to an Electronic Medical Record (EMR) to keep them synchronized with the CDR.

    Infrastructure Components

    • Master Patient Index (MPI) - The Master Patient Index (MPI) is a search portal and Record Locator Service (RLS) based on Integrating the Healthcare Enterprise (IHE) standards, which correlates and cross reference identifiers from patients and providers located within multiple disparate systems. The algorithms accurately search, match and retrieve patient records across healthcare ecosystems, including, hospitals, out-patient centers, medical laboratories, pharmacies, radiology centers or any medical facility connected to our network without requiring a social security number (SSN).  Our unique global identifier and search portal allows healthcare providers to find exchange and reference PHI while maintaining the data context and associations.
    • Integration Engine (API) - In order to communicate with disparate health systems, you need a comprehensive integration solution that can transform and route healthcare data. MASH iNetwork Integration Engine is an Application Programming Interface (API), specifically designed for Health Level Seven (HL7) message integration. It supports standards, such as; X12, XML, DiCOM, EDI, NCDPD and protocols such as; TCP/IP, HTTP/S, Files, Databases, S/FTP, JMS, Web Services, PDF/RTF Documents.  The Integration Engine is the key component to initially connect health systems together. Once an API is established, the Integration Engine works in the background and we can share information.

Privacy and Security Protection

The MASH iNetwork Platform is located at a certified SAS 70 Type II, HIPAA-Compliant Data Center with 24x7 on-site, trained and knowledgeable IT personnel, secured card/biometric access to critical areas, digital video surveillance, etc. The data center network infrastructure supports high speed, fiber-optics and Internet 2 communication protocols. Comprehensive Internal and External Security throughout system including;

    • Patient Consent and Management Tool
    • Virtual Private Network (VPN)
    • Secured Socket Layer (SSL)
    • Cisco Unified Computer System (UCS) Servers and Routers
    • SmartNet Intrusion Defense System
    • Blackshield Encryption Server and User ID Authentication
    • Two-Factor Authentication (2FA)
    • Audit Reporting and Trail Log (ATNA)

    Technical Standards

    Electronic Health Network technical architecture is based on the following standards.

 Name

Standards

HITSP

Health Information Technology Standards Panel

HL7

Health Level Seven

CCD

HL7 Continuity of Care Document

ICD-9-CM
ICD-10-CM

International Classification of Diseases,
Clinical Modification

NDC

National Drug Code

SNOMED

Systematic Nomenclature of Medicine

LOINC

Logical Observation Identifier Names and Codes

CDC

Center of Disease Control

NCPDP

National Council of Prescription Drug Programs

HIPAA

Health Insurance Portability Accountability Act

NCQA

National Committee for Quality Assurance

CPT

Current Procedural Terminology

SOA

Service Oriented Architecture

IHE

Interoperability Health Enterprise

TLS

Transport Socket Layer

 

Creative Commons License