Validation Request: Visceral Fascia Segmentation from CT Scans

Greetings everyone,

Before moving forward with a larger dataset, I would greatly appreciate expert feedback on my approach to the automated pipeline I’m developing for visceral fascia segmentation from abdominal CT scans.

Background: The visceral fascia, which is the fascial border enclosing internal organs and visceral fat in the abdominal cavity, needs to be automatically recognized and segmented. The objective is accurate (Dice >0.75) and quick (<2 min per patient) segmentation for clinical research.

Present Methodology: After segmenting the CT scan into different tissue types (skeletal muscle, visceral fat/organs, subcutaneous fat, and background), my pipeline extracts the visceral fascia boundary in the manner described below:

Separate the organ/visceral fat area (Label 3).
To slightly reduce the area, use binary erosion with two iterations.
Deduct the original mask from the eroded one: Visceral_region - eroded_region = fascia_boundary

This creates a thin boundary layer around the internal organs

Analysis Objectives:

The main goal is to analyze fascial volume and morphology in a population of young adults by automatically extracting and quantifying the visceral fascia boundary from abdominal CT scans.

Particular Data to Be Extracted:

Each patient’s visceral fascia boundary volume (cm³).
Measurements of the thickness and surface area of the face.
Fascia’s spatial distribution surrounding particular organ areas.
Variability in fascial anatomy between patients.

Final Outcome:
A fully automated, validated pipeline that produces CT scans with clinically acceptable accuracy (Dice >0.75) in less than two minutes per patient

Visceral fascia 3D segmentation masks
Quantitative measurements (surface area, volume)
Visual depictions (2D slices, 3D surface renderings)

Expert Questions:

  • Anatomical correctness: Is this definition of “visceral fascia” suitable for studies involving medical imaging? Is there another fascial layer I should be focusing on?

  • Methodology: Would edge detection algorithms (Sobel, Canny) or morphological gradient operators be better suited for boundary extraction, or is binary erosion (2 iterations) a better option?

  • Validation criteria: For fascia segmentation, what Dice coefficient threshold is deemed clinically acceptable? Should I be looking at any other metrics?

  • Clinical relevance: Should I be aware of any published literature references or established medical imaging standards for automated fascia segmentation?

Challenges:

What I’ve attempted:
used binary erosion (2 iterations) for boundary extraction after testing several fascia definitions (subcutaneous, deep, and visceral) and deciding on visceral fascia. successfully represented with accurate anatomical proportions in 3D Slicer.

What Prevents Advancement:

Anatomical uncertainty: Expert confirmation is required to determine whether the visceral fat boundary accurately depicts “visceral fascia” in a clinical setting.
Data problems: only one patient processes successfully, while 19/20 patients fail with DICOM orientation errors.
Lack of validation metrics: No ground truth for calculating the dice coefficient; unclear of acceptable alternatives
Methodology question: Should I use different algorithms or is binary erosion the standard for medical fascia extraction?

Your methodology basically sets the thickness you will see, your fascia segment will be two voxels thick everywhere, because that is how you constructed it. I can’t weigh in on other aspects of your proposed methods since I don’t know much about fascia, but you definitely can’t learn anything about how thick the fascia layer is using the proposed methods. Likewise, the volume of fascia is also not really something you are able to measure in this way; you will essentially be calculating the surface area of the organ/visceral fat segment and multiplying that times 2 voxels thick. The surface area is something you are reasonably measuring, though, and might be of interest. You don’t need the fascia segment to calculate that though, you can just measure the surface area of the organ/visceral fat segment. Also, note that medical imaging often has voxels are spaced differently in one direction than in another, so if you just use simple binary erosion, you will be taking different sized bites in different directions, and your fascia layer will be thicker in the directions where voxel spacing is thicker. That’s definitely undesirable, so you should first resample the image to ensure isotropic voxel spacing so that “2-voxels thick” is the same thickness in each direction.

To validate your method, you will need some sort of ground truth to compare to, via Dice or any other method. It’s hard to get around that if you want to be in any way quantitative. This usually involves creating (or finding elsewhere if you are very very lucky) a dataset of painstakingly manually created labeled data.

For your DICOM loading problems, you will need to solve those first. People load CTs from DICOM into Slicer all the time without any issue, so it is not a capability problem on the Slicer side. Typically, loading issues arise from invalid DICOM headers, perhaps from an overzealous anonymization step? I would suggest opening a separate question describing your loading problems and any error message information you see. Try loading these images outside of your processing pipeline to see if the issue is perhaps in your loading code or in the images themselves.

1 Like