I have a question regards the database config in X2.

If I have X2 connected to and MP50. I take my patient to the x-ray connected only to the Intellivue X2. I configure the X2 to record all alarms when we are at the transport. When I get back I connect the X2 back to the MP50. Is it possible to print the alarm automatic when I connect to the MP50 if I´m connected to Intellivue Information Clinical Network? How should I configure the MP50. The X2 I think is the same config as for the XDS solution. If anyone can help me please write.

Reading through the forum I found this explanation by Chandana Samaranayake MD for Philips. For the XDS-solution.


"And here is a brief explanation on how to configure your transport monitors to capture alarm reports to the database, and automatically print or store to a storage location whenever a connection to the XDS Print Server is available.

1. Go to config mode
2. Go to Databases>Database config. Make sure that the Print Database is set to Small or Large. The factory default is Large.
3. Go to Reports>Setup printers. Set the printer to "Database". Then select the desired paper size (this same paper size must be selected in XDS, otherwise the reports may refuse to print).
4. Go to Recordings>Setup recordings. Select Alarm, and change the recorder to "Printer". This ensures that any alarm recording will also be sent to the system printer, which is now set to "Database".
5. Go to Alarms>Alarm Recording. Select all the alarms that should trigger a capture (eg, HR red & yellow etc)
6. Go to Reports>Setup reports. Select “Realtime Rep” as the report, and change the target device to “Database”. Repeat this step with any other manual report you want to store during transport (eg. ST-MAP report, 12-lead reports).
7. Save all these changes under the monitor settings block. If the default profile and blocks are locked, you will need to create a new block, assign it to a new profile and make that profile default.

Now, whenever one of the alarms selected in step 4 is triggered, the IntelliVue will automatically capture the alarm and create an alarm recording report that will be stored in the database. The exact number of reports that can be stored depends on the types of reports etc, but a minimum of 50 single waveform alarm strips can be stored when the database size is set to “Large”. When the database is full, the monitor will display “Print job can’t queue” on the status line whenever a new recording is triggered and will not store any new recordings until the old ones are printed or deleted.

You can also manually trigger any of the reports you set in step 6, and they will also print to the database.

At any time, you can go to "Reports>Reports job list" to see the events that are waiting to be printed. You can delete them selectively (stop report), or as a batch if necessary (stop all reports).

When the monitor is connected to a PC with XDS application (direct or via network), it will automatically print the reports, or send them to a patient-specific folder as PDF, PNG or any other format as defined in the XDS application."

Hi Henke,

Yes, the workflow you have outlined will work. As for the configuration, here is what you need to do:
1. configure X2 to print reports to database (as per my post you quoted above).
2. On the MP50, configure the Report printing to "Auto print Dbs".
3. On the MP50, make sure that the central station printer is properly set up.
4. On both X2 and MP50, make sure the report paper sizes match the paper size on central station printer (which should be A4, for Sweden).

Reports stored in the database of X2 will now auto-print when connected to an MP50.

The reports will not print if the paper size of the report does not match the paper size of the central station printer. So if your report does not print, go in to the "Reports>Report Job List" on your MP50, and you should be able to see the list of reports (from both X2 and MP50) that are waiting to be printed. The reports from X2 will be tagged as "In companion". The list will also show the paper size of the report. If the paper size is wrong, you need to configure the paper size for each type of report correctly on the X2.

Sweet, work like a charm! Thank you, Chandana!

Today I tested this solution far wider. It´s possible to collect ALL information at a larm-triggering.

Now I wonder how big is the database? How many realtime waves is possible to store in it?

When should we use this solution?

Hi Henk,

The database size, (when set to "Large") is 50 pages. Some reports take up more than one page, so the number of reports you can store depends on the mix.

The real-time report shows up to 4 waves per page in landscape orientation. This report can be configured to show either "displayed waves" or "All waves". On an X2, the displayed waves will be a maximum of 3, so the report will fit on 1 page. If you set it to all waves, it may take up 2 pages, since a fully loaded X2 with a measurement sled can generate up to 7 waves.

You can use this solution in any transport scenario, where you would like to capture all or specific alarm strips, and/or manually printed reports (eg. 12-lead ECG, QT, ST, ST-MAP, graphical or tabular trends).

Thank you for your answer Chandana,
Have some more questions regarding the alarm recording and journalsystem ICIP.

When I set to capture an alarm for eg. HR, is it like the Information Center, that it captures 10 sec before the alarm and the next 20 sec. Or is it from the alarm trigger and afterwards its printing the curves?

In ICIP there is an option to capture waves storage from the Information Center database. Is this solution possible just connected to a monitor? Like if I have a MP50 with X2 docked in connected to ICIP without the information center. Is it possible to transfer this reports to ICIP from the MP50 with X2 directly without the information center?

Hi Henke,

The alarm triggered printing is different from a recording. You may have noticed that when you go in to alarm recording settings and change the recorder to "printer", the settings for pre/post recording settings are hidden. This is because when the recording device is set to "printer", the monitor creates a Realtime Report to be sent to the printer when an alarm is triggered. A realtime report always begins at the moment it is triggered - it can never be retrospective. The time duration of the strip is determined by the length of the page - if the page is in landscape orientation, there is enough space for about 11 seconds of waveforms at 25mm/sec speed.

As for your second question, yes, this is theoretically possible, but I have never tried it. ICIP picks up reports from a share, and reads the file name to determine the patient ID and timestamp for the document. So, in order to do this you would need to:
1. Make sure the print reports from XDS get to the share - as XDS does not have the credentials to print to a network share, you need to write a file watcher service that picks up reports from the XDS print folder and transfers them to the ICIP share, using authorized network credentials. This can be done with a bit of Visual Basic knowledge.
2. Make sure the filename of XDS print reports conform to ICIP document import specifications - this means, you would need to write a custom report naming script. To do this, you would need a description of the ICIP document import specifications, and a bit of Javascript programming knowledge. All you need to do is to go to the XDS website, go to the "tools" tab and request a custom printing script, edit the script to provide the required filename, then register the script on XDS.

Some time ago, I made a naming script for exporting 12-lead print reports in to Philips TraceMasterVue 12-lead archiving system. If you are interested, I could share it with you so that you can see how it works.