Oxyent Medical
Oxyent_Medical
About UsDifferent ModalitiesProductsPartnersCareersContact UsHome
 
TCProbe
NEIS
 
hd-EEG & PSG Database
Various Components
How SaaS and NEIS work Together?
PACS
Architecture
Qualia
Future Products

Products - Neuroscience Enterprise Information System (NEIS)

Delivering World’s Best Healthcare Management Solutions.

Our mission is to promote clinical safety and information sharing by delivering solutions that provide real value for patients, health providers & funders – globally.

NEIS provides an information system for managing the operations of a dense array EEG (d-EEG) laboratory in a hospital, clinic or research center. NEIS is based on Hospital Information Center (HIC) a hospital/laboratory "client side" software architecture component. It intends to provide effective and efficient diagnostic and therapeutic procedures in Neuro-Science Clinics. It aim is to achieve a three dimensional integration: in the space, in the time and among the component levels of the health services and link them to central system by means of a suitable network to exchange information both inside and outside of clinic.

Objectives of NEIS are:

  • Patient scheduling.
  • Resource management.
  • Electronic medical records keeping.
  • Both technician and physician workflow management.
  • The laboratory operations shall include following specialized functions of the dEEG.
  • Including tracking the dEEG acquisition to the networked IBM SAN based storage server..
  • Managing the workflow of local signal processing operations. Slow Wave, Artifact Detection and Spike Detection etc
  • Integrating MR image acquisition (clini/hospital PACS)
  • Scheduling and coordinating data transfer for remote jobs i.e. head modeling services and signal processing services.

Hospital Information Center:

  • NEIS middleware is called Hospital Information Center (HIC)
  • HIC is kind of Enterprise Service Bus while allow interaction, instantiation and lifetime management of components/services.
  • It describes an architecture that uses loosely coupled components to support the requirements of business processes and users.
  • A component inside HIC is a function that is well defined, self-contained, and does not depend on the context or state of other component. So each component is capable to provide a different kind of independent functionality.
  • HIC along with its components provide conceptual implementation of NOLIS requirements

 
 
© Oxyent Medical 2008-09