Slipped Capital Femoral Epiphysis

Purpose

To assist radiologists in the interpretation of pediatric hip radiographs

Tag(s)

 

Panel

 Musculoskeletal

TOUCH-AI ID

 TAI-05180011

Originator

 Jay Patti

Panel Chair

 Jay Patti

Panel Reviewers

 Musculoskeletal Panel

License

 Creative Commons 4.0

Status  Public Commenting

Clinical Implementation


Value Proposition

One cause of hip pain in the pediatric population is when the femoral head epiphysis slips before the head fuses with the femoral shaft. This is often a subtle finding with a characteristic appearance on radiograph. Identification of this finding, when present, could help the radiologist interpret pediatric hip radiographs and reduce false-negative interpretations.

Narrative(s)

A pediatric (10-year-old) patient with a history of atraumatic hip pain presents for hip radiographs. Slipped capital femoral epiphysis (SCFE) is present on the right. Because of the characteristic appearance of the hip morphology, the radiologist is warned when the images are displayed.

Workflow Description

All hip radiographs for patients ages 8 to 15 are sent to the AI engine to assess for the presence or absence of SCFE. The radiograph is processed by the algorithm, which is tuned to identify SCFE when present. The area of the image that triggered the SCFE alert is highlighted for the radiologist for review.

Considerations for Dataset Development


Procedures(s): {X-ray, Hip; X-ray, Pelvis}

View(s): {AP, Frog Leg}

 

Sex at Birth: {Male, Female}

 

Age (years): [8,15]

 

History: hip pain

 

Source: {Pediatric ER, Urgent Care facilities, general ER}

 

Anatomic Location: {Hip, Pelvis}

Technical Specifications


Inputs

DICOM Study

Procedure

XRAY, Hip; XRAY, Pelvis

Views

AP, Frog Leg

Data Type

DICOM

Modality

XRAY

Body Region

Pelvis

Anatomic Focus

Hip

Primary Outputs

Femoral Epiphysis

RadElement ID

RDE256

Definition

The status of the femoral epiphysis

Data Type

Categorical

Value Set

0-Unknown

1-Normal

2-Abnormal

Units

N/A

Public Commenting


Use cases are meant to be a primary vehicle for distributing clinical information to the developer community. They pinpoint precise scenarios within radiology workflows where potential automation could add noticeable value and establish standards for interpreting and passing corresponding common data elements. Implementing effective standards requires the perspective from all stakeholders. So to that end, we encourage your feedback on use cases.

To submit comments, please email DSIUseCases@acr.org with the use case title(s) and relevant comments by January 1, 2019. If more convenient, you may also download this use case and comment directly on the PDF. Just attach the PDF copy on the email.