HipCheck
K230045Stryker Corp. · cleared 2023-09-29 · product code QIH · Radiology
Premarket evidence — what FDA accepted
source quote (p.4)
“The software is provided to the user pre-installed on a mobile touchscreen tablet for which it has been tested for compatibility. Stryker conducted standalone performance testing on an object detection AI/ML model that is a part of the image processing pipeline.”
source quote (p.8)
“Stryker conducted standalone performance testing on an object detection AI/ML model that is a part of the image processing pipeline. Updating to HipCheck version 1.5.6's Alpha Angle algorithm has been done to enhance capabilities of the algorithm on uncommon image types (i.e., corner cases) while maintaining consistent capabilities on other image types. Extraction of the region of interest Extended Gabor filtering Binary edge detection and classification Circular Hough transformation Feature point tracing RANSAC circle matching Target circle selection”
Validation studies (2)
Bench
n=745 images
endpoints: Automatically detects the presence or absence of a hip; Finds the region of the image that contains the femur with high accuracy; Head center X coordinate is within +3.3%/-3.3; Head center Y coordinate is within +3.8%/-3.8%; Neck Angle relative to vertical is within +13.63°/-15.35°
Bench
sample size not stated
endpoints: segmentation accuracy and reliability; reliability of segmentation between Stryker personnel; reliability of the HipMap FAI Analysis by comparing clinical measurement outputs generated from the third-party segmentation (external rater vs internal rater), Stryker employee segmentations (inter-rater reliability), and iterations of segmentations performed by the same Stryker employee (intra-rater reliability).
Reported performance (3 observations)
source quote (p.11)
“Head center X coordinate is within +3.3%/-3.3”
source quote (p.11)
“Head center Y coordinate is within +3.8%/-3.8%”
source quote (p.11)
“Neck Angle relative to vertical is within +13.63°/-15.35°”
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).