I managed to get this file to work after switching <acquisitiondate>DD-MM-YYYY</acquisitiondate> to <acquisitiondate>DD/MM/YYYY</acquisitiondate>. After checking some previous discussions, I believe this was a bug that was supposed to be fixed a while back, and may be an issue again. Either way, it works now thankfully. Only problem is that age seems to be showing as "0".
I managed to get this file to work after switching <acquisitiondate>DD-MM-YYYY</acquisitiondate> to <acquisitiondate>DD/MM/YYYY</acquisitiondate>. After checking some previous discussions, I believe this was a bug that was supposed to be fixed a while back, and may be an issue again. Either way, it works now thankfully.
I managed to get this file to work after switching <acquisitiondate>07-11-2025</acquisitiondate> to <acquisitiondate>07/11/2025</acquisitiondate>. After checking some previous discussions, I believe this was a bug that was supposed to be fixed a while back, and may be an issue again. Either way, it works now thankfully.
Issue importing XML file exported from MAC 5500
Hi, Any news about this? Were you able to solve this problem?
Small correction in type used for the document title.
Added the Document Title field because it is type 2 required according to DICOM standards for DICOM encapsulated PDFs.
Thank you for this. Will you also update the compiled files?
Solved two bugs:
I finally found out the issue here. In .NET (core) the encodings aren't (pre)loaded like they are in .NET framework. I will add an update to the sources to solve this, probably today. Have to fix some stuff so it will compile with .NET8.0 as well.
Hi, Have you had any possibility to look at this? Any information would be highly appreciated. Thanks /Fredrik
Sorry for the back and forth. Just wanted to let you know that I seem to have fixed that issue by changing those posted lines of code within the PDFFormat.cs file with these lines below. It's not perfect, but now we at least have Last and First Name displayed as "LastName, FirstName" : sb.Append("Name: ") .Append(_Demographics.LastName) .Append("^") .Append(_Demographics.FirstName);
Hi MJB, thank you so much for getting back to me on this! I was able to use the latest source code and individually compile all plugoins and executables, and then manually copy the binaries into a flat folder structure, and it generally works, however the same outcome. It only ever shows the LAST (FAMILY) name, not the complete name. Would you be able to point me to the actual source file name that handles the concatenation of all the name parts into one full name so it can be added to the PDF? When...
Actually, I modified it to be a bit more flexible around the possible "Name parts" as each patient might have a middle name, or suffix etc while others don't: StringBuilder sb = new StringBuilder(); PointF point = new PointF(headerRect.X + 1.25f, headerRect.Y); float fTempY = point.Y; sb.Append("Name: ").Append(_Demographics.LastName); if (!string.IsNullOrEmpty(_Demographics.FirstName)) { sb.Append(", ").Append(_Demographics.FirstName); } if (!string.IsNullOrEmpty(_Demographics.SecondLastName)) {...
Sorry for the back and forth. Just wanted to let you know that I seem to have fixed that issue by changing those posted lines of code within the PDFFormat.cs file with these lines below. It's not perfect, but now we at least have Last and First Name displayed as "LastName, FirstName" : sb.Append("Name: ") .Append(_Demographics.LastName) .Append("^") .Append(_Demographics.FirstName);
Hi MJB, thank you so much for getting back to me on this! I was able to use the latest source code and individually compile all plugoins and executables, and then manually copy the binaries into a flat folder structure, and it generally works, however the same outcome. It only ever shows the LAST (FAMILY) name, not the complete name. Would you be able to point me to the actual source file name that handles the concatenation of all the name parts into one full name so it can be added to the PDF? When...
Hi MJB, thank you so much for getting back to me on this! I was able to use the latest source code and individually compile all plugoins and executables, and then manually copy the binaries into a flat folder structure, and it generally works, however the same outcome. It only ever shows the LAST (FAMILY) name, not the complete name. Would you be able to point me to the actual source file name that handles the concatenation of all the name parts into one full name so it can be added to the PDF? When...
Hi MJB, thank you so much for getting back to me on this! I will try to use a different .NET implementation as a first step, but is there any way you could maybe give me a head start on what the general process would be to get my own version compiled? I have Visual Studio, and I see there are Visual Studio project files included, but all my attempts to compile have failed thus far. would you maybe have something like a rough list of tasks that I should go through to get the complete project compiled?...
The code was prepared for .NET5.0 so maybe this is caused by changes in dependencies, but there is another possibility. You might be using the .NET framework solutions in stead of the new (core) .NET solutions. The PDF generated uses a hard coded textual layout. So you are on the right track by compiling it for your own format is the right track (currently at least).
Converted PDF files only show Last Name instead of Full Patient Name (LAST^FIRST^MIDDLE..)
Hi, Of course, please find the SCP-ECG file from my test patient attached. Any help with this is highly appreciated. Just let me know if you need other samples. Regards, Fredrik
Hi, I could take a look at this issue, but maybe you can provide me with an example (SCP-ECG file) to pick up this issue. With Best Regards, Maarten
It appears 64 chars is the specifications maximum limit for a segment of the PN segment (PersonName). I think this exception is on purpose to adhere to the standard.
From what I understand each PN component has a max length of 64 characters. However, it looks like I can't export when the sum of all components is > 64. Can export with 64 chars PN: acmlabtpuuuapumeuvrurbuidieidu^ecedailauuuvaacoqupunqsttssuiu^^^ Can not export with 65 chars PN: nttaqeuuaqiuioroetqnuqiicqalmu^tusnitbeneneouueoaantfeassoaial^^^ Stack trace: System.ArgumentException: nttaqeuuaqiuioroetqnuqiicqalmu^tusnitbeneneouueoaantfeassoaial^^^ Stack Trace: PersonName.ctor(String s) DICOMFormat.getName(Int32...
Hi, I have issues with the DICOM conversion. The source file is an SCP ECG using Nordic characters in the patient name and in the interpretation. Converted to DICOM these characters are replaced with question marks. Please see attachments (this is a test patient). Is there any possibility to change this?
Shortest sample code, I can write for this: using ECGConversion; string srcFormat = "SCP-ECG"; string dstFormat = "DICOM"; string srcPath = args[0]; string dstPath = args[1]; if (ECGConverter.Instance.waitForFormatSupport(srcFormat) && ECGConverter.Instance.waitForFormatSupport(dstFormat) && File.Exists(srcPath)) { IECGReader reader = ECGConverter.Instance.getReader("SCP-ECG"); using (IECGFormat src = reader.Read(srcPath)) { // here you might need to add configuration code for dst format if (ECGConverter.Instance.Convert(src,...
how to convert by C# Code from Scp-file to any file like Dicom xml pdf
Thanks for you support , i try if i got solution for find all values i put here , may be your possible help me
Can you please Explain cfg["UID Prefix"] = "1.2.345.6.7.89012.3.45.6"; or may I put GUID Id over here?
Bug fixed for some DICOM files that only have signals (no median provided).
Small corrections
I sadly don't have access to a GE based ECG system with a SQL database. I'm not actively looking into this, so no results for me.
Hello Did you ever figure out how to read the encoded WAVEFORM data from the SQL database? I have been trying to figure out how to read this as well.
I forgot to respond to your request. My question is are you sure the Assemblies are properly loaded. This is an issue in ASP.NET with IIS as well. You could manually load the assemblies by using the following function: ECGConversion.ECGConverter.AddPlugins("use_a_path");
Ecg to pdf conversion failed: Error: Can't open file
PDF of ECG is not plotting the waves similar to EcgViewer app display
Thank you very much :) @Ettinger. The solution suggested by you worked for me. I really appreciate your's efforts & the quick response from you. Thanks!
Hi, The ECG viewer uses: ECGTool.NormalizeSignal to take the median value of a lead and correct the values in each lead. The result is that (on most ECG recordings), the lead will be perfectly aligned in the 3x4 like format. However the PDF plugin does not use this functionality. It has not been build into the plug-in (yet), but if you can program you could provide the leads to the PDF plug-in so you can get a similar result.
PDF of ECG is not plotting the waves similar to EcgViewer app display
Hi Richard, I am also looking at a MUSE ECG sql dump, and am in a similar situation. Were you ever able to figure out how to parse the _WAVEFORM table's encoded data? Thank you for any help! -- Ryan
Solved an issue with .NET 2.0 version of dicom-cs, related to the removal of log4net.
Solved an issue with ECG recordings that are exported out of a VuePACS.
Solved a small bug.
It would appear the measurements are not in the right location, but I would have to verify this against the HL7 v3 stylesheet (.xsd) to be sure.
getGlobalMeasurements not work
I will look into this issue, thanks for supplying an example file.
getGlobalMeasurements not work
Hi Luca, The viewer does not support changing paper speed. However you can zoom in on the displayed recording (by using right-mouse-click). Effectively that is very similar to increasing speed and gain at the same time. For the PDF export there is an configuration item (speed) to do this. It looks like the output however will fall back into Regular when you change this field. Best Regards, Maarten
Hi, Do you know how to change speed of the paper from 25 mm/s to 50 mm/s (for a paediatrician is very useful) or maybe there is a way to change to different speeds like: 12,5; 25; 50; 100; 150 mm/s. By the way the app is great!
ECG DICOM conversion to PDF
I'm not 100% sure, but for me the PDF plug-in appears to be working. However it might be the fact that plug-ins are loaded in a separate thread. Use: ECGConversion.ECGConverter.Instance.waitForFormatSupport("PDF") (returns true when support is loaded) Other approach might be to wait for all loading of all plug-ins, but I prefer the specific wait.
ECG DICOM conversion to PDF
ECG core logic migration to .NET core latest version(5 or 6)
I have no experience with NuGet packages, but I think these packages are available now. I'm going to close this support ticket, but let me know if there is any issue or bug with the latest release (and packages).
Set back to default .NET framework 2.0
Set back to default .NET framework 2.0
Very close to a new release for this ECG toolkit. Must however still solve an issue for the PDF plug-in.
Small addition to add iTextSharp (sepcific build) to the PDF plug-in (package).
Set back to default .NET framework 2.0
Hi @Ettinger, Would it be possible to have nuget packages of these core libs: 1.dicomcs 2.ECGConversion 3.ECGCpluginaECG 4.ECGCpluginDICOM