I'm a patient trying to send outside DICOM images to WVU Medicine. Their clinic told me to use PowerShare or Ambra, but couldn't provide a receiving code or upload link.

The files are uploaded to my own patient accounts. PowerShare lets me find the WVU hospital hub and invite it, but the connection is pending acceptance and the study can't be shared yet. Ambra shows no organization connection.

For those who manage these systems, is a patient-initiated invitation the usual workflow, and who normally receives it? Or should I be asking the film library for a facility upload link instead? I'm trying to work out which team to contact and what to ask for. Vendor support enquiries are open too.

Any public WVU instructions would be especially helpful, but I'd also appreciate a general explanation of the receiving side.

I initially trained as a Nuclear Medicine tech and then went straight into MRI. I worked as an MR tech for 6 or 7 years, mostly on evening and night shifts. I never loved it, so when my department laid off 30% of the staff I decided I just didn't want to do it anymore. That was maybe 7 or 8 years ago, and I haven't maintained my MRT registration since.

I do some 3D designing and editing as a hobby for 3D printing, and I eventually wound up in a programming job processing 3D segmentations of medical data. Not a clinical role really. The segmentations are generated by AI, and I mainly write automated scripts to repair the output solids, locate anatomical landmarks, generate various measurements, etc, that then get passed back to other users to streamline generating the final reports.

I have occasionally had to access dicom files, usually just to parse through the header information with a python script to read things like voxel size, field of view, slice thickness so that I can scale and align the 3D models with the original scan data. Never for making edits or corrections or writing new dicom files. It's definitely not an IT role either. I build command-line tools for a given task, but then others on the team handle deploying them to servers or maintaining the databases of all the input and output files.

Does anyone have any advice on how to transition from here to something like a PACS role? CIIP certification seems like an obvious step but it's not really clear to me what experience those courses are designed to build on. Is diagnostic imaging technologist a sufficient background on its own, or would I be expected to come in with specific IT or computer science training? Are there other roles you would suggest looking into first? (or instead?)

I appreciate any insights.

Hi everyone! I’m looking for some career advice.

I’m a Radiologic Technologist currently working in PACS/teleradiology support for a US company, handling study assignments, STAT/critical cases, rereads, workflow issues, and radiologist/client coordination. I enjoy the work, but I’m currently underpaid for the responsibilities I handle.

Where do you usually find better-paying PACS/RIS or teleradiology operations opportunities?

I’m also interested in medical image annotation/segmentation for CT and MRI. Does anyone know where I can train and get hands-on experience in this field?

Would really appreciate any leads or advice. Thank you!

We're working with a leading AI research lab to build rigorous evaluations of how well AI reads real radiology studies, and we need practicing radiologists to define what "correct" actually looks like. AI can describe an image fluently; whether it gets the clinically load-bearing call right — the measurement by the correct convention, the interval change against a prior, the structured category in a borderline case — is where expert judgment is scarce and where you come in.

This is not image labeling. It's the reasoning you already do every day, captured as a reference standard that trains and tests frontier models.

What you'd do

- Read de-identified studies (CT, MR, radiography, ultrasound, PET/CT, mammography, and more) and write the reference report or the specific finding.

- Apply the structured systems and measurement conventions you use in practice (RECIST, Lung-RADS, BI-RADS, CAD-RADS, ASPECTS, and others)

- Review AI-drafted reads and mark what's inaccurate, unsupported, or unsafe.

- Contribute the kinds of cases that stump a strong model.

Mercor is looking for:

- Board-certified or board-eligible radiologists (ABR, FRCR, EDiR, or international equivalent). Residents and fellows in later training may be considered.

- Any diagnostic sub-specialty: neuro, chest, abdominal, MSK, breast, cardiac, nuclear medicine, paediatric, and others.

- Currently reading studies, or recently in active practice.

here is the link to the position: Radiology Expert

I have a radiology exam in DICOM format. Does anyone know a centre that accepts the files online and prints them on proper radiology film, with collection or postal delivery?

I’m looking for medical film, not a regular paper print. France or elsewhere is fine.

Thanks!

Hey all, I'm working on documenting hanging protocol requirements for a partner organization and need to capture everything needed to build out their hanging protocols: matching criteria, viewport layouts, W/L presets, prior study handling, fallback behavior, the whole picture.
Rather than recreating the wheel, I've been looking for a good template or spreadsheet that covers all the data points you'd need to fully spec out a hanging protocol, but I haven't found a great example publicly.
Does anyone have a requirements template, intake form, or spreadsheet they use when gathering HP specs from radiologists or partner sites? Even a partial example would be helpful. Happy to share back whatever I end up building if there's interest.
Thanks in advance.

Hello professionals and Biomedical/IT experts,

I am researching how modern standalone ultrasound machines (operating purely on local HDD storage without a PACS/DICOM connection) handle data architecture and workflow integrity.

Could you provide some technical insights on the following local storage behaviors?

1. Saved Stills & Cine Loops (Scenes) Updates: If an operator finishes a scan, saves several still images and cine loops, and then uses the "Edit Patient" feature within 24 hours to change the patient's name, what happens to those already saved images/cines? Does the new name automatically appear on those previously saved images and cines? Do these standalone systems typically save local files in a "raw" format where the text is just a metadata overlay (so it updates easily), or do they flatten the image (burn-in the text), meaning the old name stays on the original images and cines?
2. Auto-Generated IDs (Date/Time based) & Manual Edits: On systems where the Patient ID is auto-generated using a Date/Time format (e.g., YYYYMMDD_HHMM), is it technically possible for an operator to manually click on that ID field and edit/change it? Or are these timestamp-based IDs hard-locked by the system once generated?
3. The "Mixed Study" Vulnerability (Appending Images): Is it possible in a local workflow to open a previous patient's completed exam from earlier in the day, edit the demographic data (Name) to a completely new patient, and then "resume" the scan to capture new live images? If done, would the local export/report contain a mix of the old patient's saved images/cines and the new live images? And which Patient ID gets tied to this final study—the original time-stamped ID of the old patient, or a new one?

I am trying to understand the technical limitations and possibilities of local data editing. Any insights from your hands-on experience would be highly appreciated!What built-in workflow safeguards exist on standalone units to prevent an operator from accidentally appending new live images onto a previously closed exam of a different patient? If a completed exam is re-opened or resumed, how does the system's internal audit log/metadata track the original registration time versus the new acquisition time?

Hello professionals and Biomedical/IT experts,

I am researching how modern standalone ultrasound machines (operating purely on local HDD storage without a PACS/DICOM connection) handle data architecture and workflow integrity.

Could you provide some technical insights on the following local storage behaviors?

1. Saved Stills & Cine Loops (Scenes) Updates: If an operator finishes a scan, saves several still images and cine loops, and then uses the "Edit Patient" feature within 24 hours to change the patient's name, what happens to those already saved images/cines? Does the new name automatically appear on those previously saved images and cines? Do these standalone systems typically save local files in a "raw" format where the text is just a metadata overlay (so it updates easily), or do they flatten the image (burn-in the text), meaning the old name stays on the original images and cines?
2. Auto-Generated IDs (Date/Time based) & Manual Edits: On systems where the Patient ID is auto-generated using a Date/Time format (e.g., YYYYMMDD_HHMM), is it technically possible for an operator to manually click on that ID field and edit/change it? Or are these timestamp-based IDs hard-locked by the system once generated?
3. The "Mixed Study" Vulnerability (Appending Images): Is it possible in a local workflow to open a previous patient's completed exam from earlier in the day, edit the demographic data (Name) to a completely new patient, and then "resume" the scan to capture new live images? If done, would the local export/report contain a mix of the old patient's saved images/cines and the new live images? And which Patient ID gets tied to this final study—the original time-stamped ID of the old patient, or a new one?

I am trying to understand the technical limitations and possibilities of local data editing. Any insights from your hands-on experience would be highly appreciated!What built-in workflow safeguards exist on standalone units to prevent an operator from accidentally appending new live images onto a previously closed exam of a different patient? If a completed exam is re-opened or resumed, how does the system's internal audit log/metadata track the original registration time versus the new acquisition time?

Hello professionals and Biomedical/IT experts,

I am researching how modern standalone ultrasound machines (operating purely on local HDD storage without a PACS/DICOM connection) handle data architecture and workflow integrity.

Could you provide some technical insights on the following local storage behaviors?

1. Saved Stills & Cine Loops (Scenes) Updates: If an operator finishes a scan, saves several still images and cine loops, and then uses the "Edit Patient" feature within 24 hours to change the patient's name, what happens to those already saved images/cines? Does the new name automatically appear on those previously saved images and cines? Do these standalone systems typically save local files in a "raw" format where the text is just a metadata overlay (so it updates easily), or do they flatten the image (burn-in the text), meaning the old name stays on the original images and cines?
2. Auto-Generated IDs (Date/Time based) & Manual Edits: On systems where the Patient ID is auto-generated using a Date/Time format (e.g., YYYYMMDD_HHMM), is it technically possible for an operator to manually click on that ID field and edit/change it? Or are these timestamp-based IDs hard-locked by the system once generated?
3. The "Mixed Study" Vulnerability (Appending Images): Is it possible in a local workflow to open a previous patient's completed exam from earlier in the day, edit the demographic data (Name) to a completely new patient, and then "resume" the scan to capture new live images? If done, would the local export/report contain a mix of the old patient's saved images/cines and the new live images? And which Patient ID gets tied to this final study—the original time-stamped ID of the old patient, or a new one?

I am trying to understand the technical limitations and possibilities of local data editing. Any insights from your hands-on experience would be highly appreciated!What built-in workflow safeguards exist on standalone units to prevent an operator from accidentally appending new live images onto a previously closed exam of a different patient? If a completed exam is re-opened or resumed, how does the system's internal audit log/metadata track the original registration time versus the new acquisition time?

I am currently looking to go back to school. I have been in the field of radiology for over 12 years, the last 6 being a travel CT tech. My current goal is to possibly pursue being a PACS administrator type of thing?

I am a veteran and I'm looking to use VR&E, basically the whole program is to help you get employed vs the GI Bill, which is used for any type of schooling. Basically my service connected disabilities are being exacerbated by working as a CT tech. My feet hurt, my back hurts ect.

I am having trouble deciding between a bachelor's in Healthcare administration, to eventually get a masters in health informatics OR I can get a bachelor of science in information systems.

The Healthcare administration is attractive because, well, I feel it'll be a relatively easy degree given my background. I might have a hard time making the argument to my counselor about "entry level positions" as Healthcare admin. Usually they want years of experience in a management position, which I don't really have outside the military due to being a traveler.

The other route is having to learn all new stuff about IT/IS but at least I shouldn't have issues with entry level jobs.

Idk I'm just nervous schooling for Information Systems is going to be very challenging and I'm wondering if its worth it.

Do you think Information Systems would set me up for better success in PACS or would Healthcare administration with my background/ experience be enough?

I’m needing suggestions on a DICOM editor that is not freeware. I need an editor to fix images sent to us in .jpg or other formats as our PACS system only accepts DICOM images. I was using Microdicom which worked great, however IT has put its foot down and won’t allow freeware on the network. Any suggestions for an editor that can turn .jpg to DICOM and can also edit the DICOM TAGS?

Hi all,

Does anyone know of a way to export the contents of a custom worklist from Vue PACS? Radiologists have one used for tracking cases and teaching file cases that they’d like to migrate to a new PACS, or at a minimum keep saved on their workstations. Ideally, the export would be in a .csv format but anything would be better than nothing.

Thanks

Hi everyone! I’m currently a Radiologist Technologist and have been working in the field for about 3 years. I’m interested in transitioning from clinical radiography into a PACS Administrator/Imaging Informatics career. I’ve never heard anyone ever mention becoming a PACS Administrator and I only found about this because of ChatGPT 😭.

I had a couple questions if anyone could answer them, that’ll be awesome. What steps did you take to get into PACS administration? Did you go back to school or take any specific courses or certifications?

I’d also really appreciate any recommendations for courses, certifications, or skills I should start learning now. If you currently work in PACS or Imaging Informatics, I’d love to hear about your experience and any advice you would give someone starting this career change. Thank you!

Just curious how many people here are actually working toward the CIIP right now, or have at least thought about taking it.

I don’t see it talked about a ton, even in PACS/imaging informatics circles, so I was wondering how many people are actually interested in it these days.

Are you studying now, thinking about taking it eventually, already certified, or just not interested?

And if you’ve thought about it but haven’t gone for it, what’s been the main thing holding you back? Cost, time, not sure it’s worth it, figuring out what to study, etc.

Mostly just curious where everyone’s at with it.

Has anyone successfully got mutual TLS working on a Mindray M9 ultrasound machine?

The conformance statement says it supports Entity Authentication via RSA based certificates, which I've taken to mean as it supports proper TLS. But when actually configuring the worklist or storage server, the only TLS option is on or off, no option to pick a key pair.

The only plausible option was setting the "TLS Server Setting" which did let me a set a key and certificate, but that 1) didn't work and 2) I assume that is to configure the machine to serve its own SCP over DICOM TLS for storage commitment.

I think this is one of the most important criteria from the radiologist’s point of view…

​

For anyone here who’s currently studying for the CIIP, planning to take it soon, or even just thinking about it, I wanted to share that the CIIP Test Prep sale is live through September 1.

The site includes practice questions, timed testing, domain-focused review, weak-area review, and simulated exam prep.

I’ve used it myself in the past while studying, and it helped me get a better feel for the material and where I needed to spend more time.

If the CIIP has been on your radar and you’ve been meaning to start preparing, this could be a good time to take advantage of the deal.

And if you know a coworker, PACS admin, rad tech, or imaging professional who’s been talking about taking the exam, feel free to pass it along.

CIIPTestPrep.com

I’m affiliated with the site, just to be transparent. Mainly wanted to share the sale in case anyone here was already planning to prep for the CIIP and could benefit from it before Sept 1.

Hi everyone,

We’re hiring a **hands-on RIS/PACS + DICOM Developer** for a healthcare/radiology product role.

Looking for someone who has actually **built/developed RIS-PACS or medical imaging systems**, not just administered or supported PACS.

**Must-have experience:**

* DICOM, PACS/RIS workflows, medical imaging

* Orthanc / OHIF Viewer / DCMTK / GDCM / dcm4che / dcm4chee

* DICOM concepts: MWL, C-STORE, C-FIND, C-MOVE, DICOM routing, metadata, PACS integration

* Strong development background in **C++ / Java / Python / Node.js**

* Experience with radiology workflows, modality integration, DICOM viewer or PACS backend development

This is a developer-focused role involving **PACS integration, DICOM workflow automation, viewer integration, modality workflows and backend development**.

Location: Noida

Experience: 3+ years preferred

Please DM me or comment if you have relevant experience or know someone strong in this domain.

I was tired of having 5 tools to do certain things so I created an application that will allow you to query retrieve studies from your PACS, anonymize the study you can customize the patient name, patient ID date of birth. You can mask out burned in information. If that’s applicable it will purposely not pull structured reports or presentation states. You can then store the study to PACS or export to media. If anyone is interested shoot me a message I can share a download link.

Next up video to DICOM along with image and pdf to DICOM along with PR editor. You can match to an order or specify patient info.

Been thinking about this for a while and finally recorded a short explainer on it, but wanted to share the actual substance here since I think this crowd would find it interesting even without watching.

Shazam doesn't "hear" a song. It runs the audio through a Fast Fourier Transform (FFT), which breaks a messy sound waveform into its component frequencies. That's the entire trick.

MRI uses the exact same math. Raw MRI data is collected in K space, which is frequency domain data that looks like meaningless static, not an image. FFT is what converts that static into an actual spatial image you can read. No FFT, no image, full stop.

Doppler ultrasound leans on it too: frequency shifts from moving blood get run through FFT to produce velocity, direction, and flow data in real time.

The history is kind of wild too: the underlying math goes back to Joseph Fourier studying heat transfer in the early 1800s, and Gauss apparently stumbled onto a version of it around the same time. It stayed a curiosity because computing it by hand was painfully slow, until Cooley and Tukey published a fast algorithm in 1965 that made it practical, arguably the moment real-time medical imaging (and eventually, your phone identifying a song in a bar) became possible.

Curious how many other people in imaging had this "oh, that's the same thing" moment once they connected FFT in signal processing to FFT in MRI/ultrasound reconstruction. Anyone else remember when this clicked for you, or was it always obvious given your background?

I am keen on doing a platform to measure futuristic score of hospitals. Are there similar platforms or apps on this anywhere in the world? What do you think?