This HTML5 document contains 9 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
n3http://www.openvoc.eu/poi#
schemahttp://schema.org/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.yelp.com/Review/id/
n6http://data.yelp.com/Business/id/
revhttp://purl.org/stuff/rev#
xsdhhttp://www.w3.org/2001/XMLSchema#
n7http://data.yelp.com/User/id/

Statements

Subject Item
n2:o1DdIDWEcR4ZymijeGMeXg
rdf:type
rev:Review
schema:dateCreated
2016-09-30T00:00:00
schema:itemReviewed
n6:GCD5aEHFDisv0JTcRLOEsg
n3:funnyReviews
1
rev:rating
2
n3:usefulReviews
5
rev:text
My experience at the office was fine. I hurt my knee. Dr. Yu examined me and based on my pain responses determined that my exam was normal; however, I had torn my FCL before - a somewhat unusual injury that might make the pain response hard to elicit during physical examination - so Dr. Yu told me he was "on the fence" as to whether to do an MRI, and encouraged me to call back if I decided I wanted to schedule. I left and thereafter did decide that I would feel more comfortable definitively ruling out another tear or some other issue with an MRI. I have now probably called the office 5-7 times with no response. Initially when I called, the office told me that the delay in scheduling was due to an issue with my insurance - they were reportedly waiting on a prior authorization. After two weeks of that, I decided to call my insurance myself, which told me that prior authorization was not necessary - my doctor just needed to call and order the study. After that I called Total Sports another 3 or so times - no one answered the phone, and no one returned my calls. It has now been about a month since I hurt my knee. I coach wrestling and have been prevented from returning to full activity because I have no concrete assurance that there is nothing wrong there. The lack of after-the-fact attention and follow-through has been very frustrating and is what prompted me to write this negative review.
n3:coolReviews
0
rev:reviewer
n7:BPFFIhg1Utqu8nzdEAlXeA