Skip to main content

在美国凡涉及钱和账单的事情自己首先要搞清楚。
从叙述上看,lz显然不知道自己的保险包括哪些,怎么付费。想当然以为cover就是自
己一个子都都不掏。任何保险cover的时候最基本的是copay deductable 和 自负比例
。 甚至门诊急诊住院检查都各不相同。买保险的时候就该问清楚。
然后是对信用体系搞清楚。
什么情况会损失信用,损失信用会怎么样,承担多大后果。
这个事情显然应该和医院的bill部门好好谈谈,最好是医院bill部门把账单弄回来,再
付。然后还要个书面说明给你的信用中心,说明这个事情不是你的责任,不能进入你的
信用报告。
美国是自由资本主义,所有给你提供服务的地方,都是满脑子想赚钱,bill的事情自己
不弄清楚,肯定是自己的钱包倒霉


1,楼主应该清楚自已保险,哪些cover, 哪些不cover,或者是cover 多少。it is
always patient's responsibility to call insurance for this info before you
go see Doc or any test.
医生,护士不会知道你的保险,不要relay on 他们。
2, 不要责怪医生。如果体险结果有异样,医生有责任,义务做进一歩检查,当然你可以
不做,这是你的权利,但是医生不能忽视这些异常,因为这是他(她)的责任。
malpractice, 没人敢忽悠这个。
3,钱不多。如果楼主经济上还好,就付了吧,下一次记得给保险公司打电话问清楚。
如果经济上不宽松,跟医院协商一下,应该可以找到解决问题的办法。


一点常识。在美国通常医生所在单位和医院分别属于不同机构,各管各的账单。医生和
护士所说的没有问题。

建议:

1)马上把账单付了。
2)查3个信用局的credit report. 如果有不良记录(collection accounts),
dispute.
(官方免费网站)
https://www.annualcreditreport.com/cra/index.jsp
3)无论怎样,算给自己上了一课。





楼主刚上班,保险的细则没搞明白,其实大家刚开始都一样,保险里付费细则不好搞懂
,经常要问过来人。 楼主的保险和大部分钓丝的一样,大的检查项目和住院治疗病人
都要付deductible (250,750,甚至还有上千的)和 co-insurance (10%,20%, 甚至
还有更高的,所以即便这个检查项目是covered,保险公司付医生医院钱的时会扣掉
deductible 和 co-insurance 的这部份,随后医生医院就会给你寄账单要这部分钱。
有的时候医生医院会根据你的保险,事先算好你要付的deductible 和 co-insurance,
作检查时候就问你要, 当然这种情况会好一点,至少你知道要付多少,不爽了还可以
不作,不过大部分人也只能忍痛割肉去做,毕竟身体比什么都重要。

我去年肩膀突然疼得厉害,胳膊都抬不起来,去看了医生,照了x光没问题,又建议我
做MRI,到护士拿预约,算了下deductible 和 co-insurance要300多,也只能咬牙作了
。结果也没查出什么,医生就给开了管扶他林, 抹了好几天没见效,后来有个朋友建
议搞个热敷垫热敷,一周后就好多了。话说之后MRI又来账单,一看原来读片的放射科
医生的co-insurance还没付。 最后一个MRI自己掏了400多。这也是美国医疗制度的优
越性之一。



right
如果不是法院判的,坚决dispute!
【 在 yangguo1 (杨过) 的大作中提到: 】
: I am working for a collection agency and let me tell the tricks.
: Call the collection agency and writing a letter to them to formally
dispute
: the charge, the agency will return the bill to your landlord.
: The dispute or the attempt from a collection agency won't affect your
credit
:  score.
: Some bad agencies may try to scare you. don't be afraid of them, ask them
to
:  show you paper evidence that you agreed to pay that charge.
: More than likely, the charge will be dropped.
: Good luck.
:  

Comments

Popular posts from this blog

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec