Recent Posts

Pages: [1] 2 3 ... 10
FAQ / What part of the DICOM standard is supported?
« Last post by David on December 06, 2017, 11:28:30 am »
Medmont Studio software implements C-STORE and C-Find capability. The C-FIND command is used to import patient demographics from a work list server (avoid double data entry) while the C-STORE is used to submit print reports to a storage server.

Studio supports submitting reports in two formats;
1) EncapsulatedPDF and
2) Multi Frame True Colour Secondary Capture.

Medmont Studio also supports the ability to import DICOM files into the DV2000 diagnostic imaging module. The DICOM Watcher utility is provided to monitor a folder on your hard drive for new DICOM files. If it detects a new file it will automatically import that DICOM file, it does not require the DV2000 capture window to be opened. DICOM files, imported this way, must be in the Visible Light Photographic Image Class format.

A DV2000 license is required to import DICOM images into the DV2000 module.
Issues/Problems / Re: video mode processing
« Last post by Palani on October 10, 2017, 10:04:51 am »
Hi John,
I rang you this morning and someone told me that you are with a patient.
Can you please call me on 0392590811 ?
Issues/Problems / Re: video mode processing
« Last post by John Boulos on October 07, 2017, 08:14:57 am »
Hi all
I have a similar issue, the images (static) have been captured, but I don't know how to view the video. Can anyone provide a tip?
Modemont version 5.3.5
The Tear Film Quality map shows the tear film surface quality (TFSQ) over the surface of the eye at a given point in time.   This is basically a measurement at each point on the eye of local variability in the ring width.  Typically local tear film break down is characterized by a large variability in the ring width.

Mathematically the TFSQ at a point is calculated by finding the standard deviation (SD) in the widths of the surrounding rings 10 degrees either side of the point.  The TFSQ  at the point is then calculated as percentage of the square of the SD normalized by the average width (W) between the rings:

TFSQ = 100 * (SD / Average W)^2

A local TFSQ value of greater than 0.3 typically indicates that there is some tear film breakup going on in that area.

The TFSQ Area attribute (which is graphed over time in the bottom graph for Tear Film Exams) is the percentage of the eye, within a 7mm chord, that has a local TFSQ value greater than 0.3 (ie is in breakup).  So a value of 5 in the graph indicates that 5% of the eye surface has tear film breakup.

The Auto Tear Film Breakup Time (TBUT) is calculated by finding the first two consecutive frames where the TFSQ Area exceeds 5%.

The Tear Film Breakup map shows the time (in seconds) until the TFSQ exceeds 0.3 for each point on the cornea (ie the time till breakup).   It is useful for understanding how the tear film breakup progresses over time.
Feature Discussions & Suggestions / Re: Composite topography maps - best way to take
« Last post by Grant on August 31, 2017, 09:26:12 am »
While placido topography is more accurate toward the center, the drop off in accuracy for the E300 is very small.    It is more important that you have as large an overlap as possible between the captured images while still being able to capture rings right out to the limbus.   The new Composite Capture wizard in Version 6 makes getting this right much easier by providing guidance and auto capturing once the patient fixation is in the right area.
Issues/Problems / Re: Medmont Studio Keeps asking for serial number.
« Last post by aylabogoni on August 31, 2017, 04:25:44 am »
Michael Eldridge, thank you so much! Problem solved!  :D

Best regards,

Issues/Problems / Re: Medmont Studio Keeps asking for serial number.
« Last post by Michael on August 15, 2017, 09:56:40 am »
Hi there,

The issue you are having is because you currently don't have a 'default' E300 device selected. This may not have been the case before because you may have only had one device present. If you have recently imported exams from a different device, you will now have multiple devices in Medmont Studio and it wont know which one you are trying to connect to.

To fix this follow these instructions:
  • Start Medmont Studio
  • From the menu select Configure > E300 > Instrument Setup
  • You will now be presented with a list of E300 devices that have calibration files installed on the system. Select the serial number of your connected E300 and then click on the Set as Default button.
You should now be able to start an E300 exam and it will connect straight to the device with this serial number.

Kind Regards
Michael Eldridge
Issues/Problems / Medmont Studio Keeps asking for serial number.
« Last post by aylabogoni on August 15, 2017, 05:22:14 am »

I'm from Brazil. My Medmont E-300 serial number is E32572 and my Medmont Studio Version is 5.3.6. The computer runs Windows 10.
It was everything alright until last month, when it started asking for the Serial Number everytime before I make a new measurement (even if the patient already has previous exams).
It happens in the Home display, when I select the "Corneal Topography" button.
What should I do? I have tried the configuration menu, but I couldn't find any solution.

Thanks for your attention.
There is already functionality within Medmont Studio to export selected images (and associated patient data) to a folder on the PC and then launch a third party software application. A reference to the image is passed to the third party software application for processing. This action is initiated from a single button press on the Medmont Studio main menu. It would be up to the engineers at Monkey Software to write some bridging software to import the image into their software to be used with their mail merge facility. I would encourage you to contact Monkey Software and ask them to contact Medmont if they need technical assistance with the interface.
Issues/Problems / Re: Problem of creating custom RGP lens design "series"?
« Last post by Michael on August 11, 2017, 09:21:48 am »
Hi Forrest,

Apologies for the delay in responding. We have had a lot going on here at Medmont and a few of these posts have been missed in the action.

As I am sure you are aware, we have received your lens details ready for adding to the contact lens database inside Medmont Studio. When we are able to start work on your designs a software engineer will be in touch to further clarify points on your design and get your review of our implementation.

Kind Regards
Michael Eldridge
Pages: [1] 2 3 ... 10