There&#x27;s a balance to be struck, for sure, but cost transparency as an alternative to complete and total cost opacity is a move in the right direction.<p>My daughter fell at lacrosse practice and hurt her wrist.  We had an x-ray, which proved inconclusive with the swelling, another x-ray after the swelling subsided, which also resulted in an inconclusive result, followed by an MRI which indicated a bad sprain, for which we ended up getting a very cast-like splint.<p>This is basically the same as what we thought from the initial x-ray, as even then the doctor was advocating for a splint in the absence of an obvious break.<p>If costs were more apparent, we probably would have had an x-ray once, and then gone with the splint, but price opacity and insurance obfuscated the costs enough that we naively opted for the more diagnostic approach, which proved to cost a lot more than just having gone with the splint initially.  As a developer, I&#x27;m inclined towards the &quot;know what you&#x27;re fixing before building patches&quot; approach, so the diagnostic approach was logical to me, but had I known that the end result was basically the same either way, I could have saved myself the cost of an x-ray and MRI and just skipped to debugging.