back



 to main page

 

Kontakt

 

Patient databases
(EPR, HIS, RIS, LIS, CIS, PACS etc)
 
and communication platform.

Our global offers for the digitizing of hospitals may integrate several information systems (EPR, HIS, RIS, LIS, CIS, PACS, endoscopy software, gynaecology software, etc) produced by selected partners.

Those systems could be embedded in others, or at least will be perfectly integrated to each other

  • with communications in HL7, DICOM or other standard if any
  • with or without overlapping and redundancy of the archiving
  • with or without master patient index.
When the integration between the pre-existing systems faces any problem (for instance: incomplete system, obsolete concept, obstructive producer, absence of master patient index, etc…) a communication platform can be proposed by Pansys.

The HIS proposed by Pansys is together global and customizable. Its conceptual priorities are the improvement of the medical workflow and the facilitation of the all the data transfers in the hospital.

The LIS (laboratory information system) either is autonomous and can be integrated with any HIS, or is natively embedded in the HIS by being a part of a global system produced by the same developers.

The integration between the RIS and the PACS aims mainly, either at the synchronized viewing of images and data/texts, or at the transfer of the respective data from one system to the other.

But when together the RIS and the PACS have to be replaced, the easiest, safest and cheapest way consists of acquiring one single system, named in that case RMS (radiology management system), conceptually based on the concept of "one single bag per patient" and providing globally all the features of PACS (diagnostic viewing, teleradiology, image distribution, archive) and of RIS (scheduling, worklist server, reporting).

That software can be used as clinical management system, and provides then the tools dedicated to cardiologists (CIS = cardiology information system), to gynaecologists (gynaecology information system), or to gastroenterologists (endoscopy software), besides the radiology management system.

Regarding specially the PACS, our proposal provides the suitable security, which protects the confidentiality and the integrity of the data, and a selectable compression, which increases the speed of the transmission and the effective storage capacity and decreases the cost to the same extent.

Several solutions of archiving and of backup are available:

  • on-line with or without near-line
  • on server + RAID or NAS or SAN
  • with or without tape back-up
  • with or without archive filer
The access to the data can be protected by a failover, and optimally distributed by a load balance.

As basic hardware of archiving medium of that PACS we first propose a RAID system, as extension of a server [see: Hardware]. Its storage capacity can be later increased almost linearly.
That cheap, robust and stable solution provides an on-line access to the archived images, even in the long term [see:
Transmission of digital images].
That solution is the best compromise of capacity=cost, security, and speed of access (on-line access).

But the software must be appropriate. The PACS that we propose offers a multiple document storage path that allows an extensible storage capacity. It can so deal with any size of RAID, NAS or SAN.

Moreover that PACS provides a hierarchical storage management able to store differently the images on one hand on the server (+ its eventual RAID extension), on the other hand on any other support (like another server, RAID, NAS, SAN, or an Enterprise Archive, or a remote datacenter, or a jukebox using CDs, or DVDs, or tapes, etc).
So the most recent images are stored on the server ( + its eventual RAID extension) where the oldest images are deleted on a FIFO-way (first in, first out).
But all the images, even old, remain preserved on the second support (NAS, SAN, Enterprise Archive, external datacenter, jukebox). Those images, being so not more "on-line" can be fetched "near-line" within a short delay.
About our proposals of secondary archive, see our section: Hardware