When I told them about it, their response was pretty much "Oh, too bad - once that username is created, it is there for life. You will have to shut down that account and create a new one", meaning I lose all the benefits I got from the promotional transfer.
So I just put up with a wrong first name whenever I sign on or ask for support from them. I still think it is strange that some second or third level support engineer can't just change that info in the database for me, after the proper authentication. I can't believe that something so easy to create over the phone can be so hard to change over the phone.
I actually kinda enjoy these minor discrepancies, because it exposes who has sold my customer data and to whom -- though I've never gone as far as giving anyone intentionally incorrect data with this purpose in mind. I remember my parents also being amused with these copied mistakes, and with greater frequency. Seems plausible that the error rate goes down when most of my utilities/accounts were self-created online instead of typed in from a handwritten form or during an onboarding phonecall.
Me: That's ABCD as in Alpha, Bravo, Charlie, Delta. Them: So, that's Alpha, Burger, er, Charles, Diamond??
My last job used radios for site communication, and everyone had to use the NATO phonetics, and was provided with a cheat sheet for learning. You'd think that would be something they could tape up in every cube in a call center...
It's not a natural law that phone audio quality has to suck.
(Teachers knew in high school for three or four years never quite figured out whether my surname was the Danish or the German variation of a common patronymic. I feel your pain.)
Its very hard for CS agents to spell correctly.
He first told them to cancel the deal, then tried again, same wrong apartment number registered, he called the ISP and the response was, "yes we know it's the wrong one, but we've mapped that apartment to your apartment on our side, so all is good."
How would it play out legally if I sign a contract where delivery is to be made to X but I want it to Y, but they tell me to sign it anyways because they can fix it in their end. I mean, what I signed would not be what I wanted, how so I prove this if my wish is not fulfilled?
Were you not able to direct the person on the phone to recreate the account for you, and to include all benefits, and then some for the inconvenience?
I've always gotten what I wanted from US ISPs. Say what you want about their evil business practices, but it sure is easy to get whatever weird shit you're asking for with simple "ok, you can't give me this? Please escalate to your manager / please transfer me to retention."
In my experience with phone staff in any large org, once an error is committed, it's generally a one-way street. Attempts to get the person to fix things lead to worse and worse problems, more damage, more problems.
My experience with T-Mobile seems typical: simply wanted to take monthly plans of myself and wife (both with TMbl) and combine into a single family plan. By the time the ordeal was done, I'd forfeit the remainder of my month's payment into the plan, had no functional phone, was being bounced between two different departments neither of whom could fix it, and both of whom insisted the other was the one to fix it.
In the end I just let the money go and moved my phone number onto a competitor. I have no faith the competitor will fare better if some error is made.
My ISP actually closed my contract earlier this year. Out of the blue, I got a phone call from someone about "my cancellation". After some puzzled minutes the operator figured out that someone else with the same name cancelled their account but didn't state a customer ID or his address, so they went on to cancel mine. The operator told me he'd correct this, but a month later my internet access went down all the same.
After some back and forth to get it back up, the next supporter I had on the line said that they actually tried to cancel the cancellation, "but it was already too late for that" and the system didn't let them. That was surely one of the bigger WTF moments I had with support so far.
So, I've had pretty much your exact experience with T-Mobile, but I never did this. I just called and called and called. I'd stay on hold while I lifted or was driving around, it was no skin off my bones. When I had a person, I'd always repeat "this is exactly I want in no uncertain terms. Do you understand? Can you get me this? No? Please transfer me to your supervisor / retention." For some reason, they'd always transfer me up. I've almost never heard "no" to a transfer request. I've never not gotten what I wanted.
So maybe I'm just waaaaay more annoyingly persistent? :P I probably have notes raging at my dickishness on every account I hold.
I have no idea where this info is stored as the details on my billing / shipping addresses have my correct (full) name.
So it's better for them to send a mail to LongName LastName than to LongNameSomethingHere where the last name fell outside of the tag
And as your card shows, the full name is on the DB
If your name tags don't work with slightly longer names, your name tags are broken, not the names.
OTOH these days I'm happy when receiving mail from the US if the address wasn't mutilated by converting Unicode to ASCII or using HTML escapes. Especially when ordering things to my company address, which has an ampersand in the company name and an umlaut in the city.
They're doing exactly what you mentioned in the first line, so big names are identifiable on letters with size limits for the address
Trust me - I seen things like this before (with huge companies where dev soft costed millions of USD). Probably same story here.
Often /that/ doesn't get updated when they update the username, leading to mass confusing since external tooling will use that as the subject identifier instead of actually being given a proper internal identifier. (Offhand I can't recall if any particular standard happens to require that such an identifier start with a letter; at least one probably does.)
For systems where cell-level change logging on the order of years is a requirement, this doesn't surprise me. Many providers would rather prohibit edits rather than risk having to greatly expand logging requirements.
So what happens if you change your name, e.g. because of marriage?
Twitch.
When I moved house I had to make up a new username/email. They couldn't just change my address, they had to create a whole new account.
I'm looking at you, TPG. Truth be told, they have been a fine ISP, other than that WTF.
Bureaucracy won again. Until we got a different operator at the ISP who worked out that they could add my name as if the account was landlord & renter scenario, so there could be an owner and another who was responsible for payment.
Changing a name that was correct is a totally different problem from a typo at ingest.
Same works on Discord too. There you can change your name whenever the hell you feel like it. Again, doesn't stop most people recognising you.
From what I've observed, HN encourages people to use consistent identities, not necessarily real names. 'dang has mentioned a number of times that pseudonymity is fine.
There are always exceptions. I have a friend who had a bad history with her family, so she really wanted to take her husband's name. But I still believe that keeping your pre-married name is usually the best choice if you don't want your identity to be lost or subsumed.
Perhaps that is something that's worth allowing, and iirc dang et al have made some vague statements that they may be interested in allowing that at some point, but the ramifications would be substantial. This isn't something that should be taken lightly, nor should it be expected/implicit that a social site will accommodate new identities on-demand.
And?
My anonymous (to everyone but the NSA) username will be a different anonymous username. The karma/privileges are entirely dependent on the quality of my posts, not some inherent value of the username. Also the posts that generated that karma would still be there under the new username.
I'm not too concerned either way , but I don't see why that would be a big deal.
Anyway, I suspect that if you e-mail HN mods, they could be able to correct your username in no time. But making it any easier than that would, IMO, be harmful to community.
Yes, you don't. But forum managers have been aware of the issue for years
It's a feature that's very easily abused.
Despite your explanation, I still don't see any actual damage. I made up the identifier in the first place. Why should anyone care if I change it? All my posts will remain my posts.
The only thing is that maybe some people who remember my posts with the old username won't recognize the new name as the same poster, which I don't see as a significant issue. Is that a problem for forum managers? I would have thought they would have problems with people creating multiple new accounts and spamming, not changing the username of existing accounts.
Please explain, I'm honestly curious. Maybe I'm missing something?
Yes, because people will abuse it. If you keep track of violations (especially in moderated forums) it's important to know who did what. And while your primary key on the DB might still be the same, people don't know it, they know your nickname.
Some people would change it every time they comment just for the sake of it
New account creations have some kind of gatekeeping/email verification so it's not as efficient, and admins have ways of checking if this was done with the purpose of evading a ban for example
But if you want to change it because you made a typo or for a similar reason admins usually let you do it (they have to change it for you though)
Regulatory, perhaps?
And despite the fact that many real world problems can be better modeled with an append only log and a derived state, somehow 99% of software systems opt to store the derived state only.
In France too where there is some provisions to change its name. Someone in my town who was running a business did it. His family name was Hittler, which has you guess was quite heavy to handle, and change it for Hittier.
[1] http://www.taipeitimes.com/News/taiwan/archives/2010/05/30/2...
Women usually take the surname of their husbands in western countries.
Edit: oh, sorry I thought you were being serious.
Jokes and such are frowned upon on HN and many people probably see sarcasm the same way, so you risk getting downvoted too.
In order to avoid adding noise (in the form of responses from people who didn't realise you weren't serious), I would suggest to refrain from sarcastic comments.
Also, Poe's Law. https://en.wikipedia.org/wiki/Poe%27s_law
I guess the issue is that the future is not evenly distributed.
They kept billing my defunct account, despite dozens of attempts to correct.
My small claims suit for my expenses was dismissed due to a binding arbritration clause. As a then 22 year old, that was about all I had the time to do.
I've likewise been extremely interested in reforming EMRs. It's a precarious field to get into, but I am definitely very interested in pursuing it (perhaps after medical school, though).
The culture seems to be that individual departments get to decide their own software, based only on their needs. Interoperability is not on their list.
So radiology buys what they want, admissions buys what they want, and so forth.
Then, the department that has the least clout and direct funding (IT) has to tie it all together.
There are some actual standards like HL7, and some generally accepted non-standards like Orsos, but they are all too loose to solve the problem completely.
Changing a name is hard partially because it is one of the identifiers that tie the mess together.
I think that's a good thing by itself, various parts of a hospital are incredibly specialized and a one size fits all solution will never work. The alternative is some much higher level of management deciding what everyone buys.
HL7 needs to be scrapped though, it does nothing to achieve inter-operability, it's just there to make hospital managers think that it exists and keep smaller players out of the market.
So things like "optional" integration modules go unpurchased. Contract terms don't address basic integration needs, etc.
Or, a specialized department has a software bake off, finds 3 solutions of equal value to them, and picks one at random. Not knowing it's the one least likely to fit in the larger picture.
Or, crossover software that serves more than one department is purchased by only one, with no discussion.
Basically, for whatever reason, healthcare is just more territorial and segregated than most other companies I've worked in.
I was doing training at one hospital where, when they admitted a patient to the floor from the ED, had to print out the entire EMR, because the EMR in the ED and the floor was not compatible. Insanity.
By all stakeholders I mean:
* The department needing the software.
* The department integrating the software (usually IT).
* The department(s) consuming the data.
* Any other departments that interact with the above dataflow (IE does it contradict things they are/plan to do?).
* Whoever signs off on the check.
The formal veto would include written problems with the proposal "this is not a good idea as proposed because Z" and/or "for this to work we need X as a requirement, but it isn't in the proposed spec".There are some with good user feedback for GPs and individual doctors like Elation EMR http://www.softwareadvice.com/medical/elation-emr-profile/
but I haven't seen any people really like for hospitals. Epic is often the best reviewed and a lot of people hate it.
I went to a hackathon for nurses three months ago where they were complaining the hospital systems are crap and asking for fixes and thought oh I'll knock something up and have not got very far - in three months you can't even read what other people have tried really - there are over 300 emr systems listed on softwareadvice.com and I read elsewhere the average hospital uses about 80 separate systems. It's a complicated mess.
I've been working on an idea for something like Dropbox with a viewer to display the different formats, HL7&v2, FHIR etc with basic search as a step up from people having to print stuff out and fax it. Not really an EMR but a tool to view record which could maybe be extended. Dunno if that has legs or if anyone had done it already?
Not sure what your intended market is, assuming internal for a hospital, but that doesn't sound like a usable idea to me. How does a typical enduser get the HL7 out to put in your dropbox? Most health systems won't let you just export a HL7 without paying the vendor through the nose for an interface.
There are so many inefficiencies in the typical hospital that there has to be ideas there, unfortunately there's usually some silly political issue or crazy Catch-22 type situation that stops common sense stuff from being able to be implemented.
There must be some way better than this stuff: https://www.quora.com/How-do-Medical-Records-go-from-institu...
Maybe the nurses didn't know how to do it, but it can definitely be done.
Not saying there aren't other glaring inefficiencies (outsourced useless IT helpdesk especially), but changing patient demographic info is not one of them.
It still screams 'poor design' and 'couldn't be bothered to test'.
Please help fix them, there are so many examples of shocking UI in health. So many of them look like first year uni projects by middling level programmers.
Also, sometimes only particular people (probably Admissions Dept) would have the permissions/knowledge necessary to edit that info. So maybe the nurses couldn't fix it but surely there would have been people in that hospital that could have fixed an incorrect name, had they been notified. They were probably who made the error in the first place!
It could be SAP or some other old fashion ERP system. Or some old Java/C# application built for the hospital. These have usually in common a very crude old fashion UI and things like changing a record is overly complex.
Often also the workers don't know the program good enough. So they only know the standard use case. If you fall out of the 95% use case, you get into a lot of trouble because of their inexperience with the application. If they try new things put to mitigate the issue, it's better to ask for their boss or things can go worse.
Clients have been asking for years to get browser-like functionalities, getting a form with only the fields they really need and nothing that can be determined automatically. But SAP has been improving for years, and now they are offering jQuery in disguise https://sapui5.hana.ondemand.com/
It's hard to blame bad UI on SAP when they are pushing for the opposite.
https://www.aclu.org/other/5-problems-national-id-cards
>> Reason #2: An ID card system will lead to a slippery slope of surveillance and monitoring of citizens.
I think "they" are already monitoring everything I do. Maybe this would have mattered more to me before I had a smartphone, passport, bank account, social media accounts, etc. If I wanted to live off the grid with no electricity & only using trained ninja squirrels to buy things with unmarked bills on my behalf, I would certainly not want to be forced to into having a national ID card. I'm not advocating monitoring. I just feel a national ID card wouldn't be much different than my current situation.
There's no reason why ID cards would lead to more or less secure data collection than today.
"Hi I'm Travis Johnson42"
There is one reason why it is so. When they make such error, you must take effort, time and money to fix it. So if hospital can spend "their" money on system that can fix and/or catch such errors (+staff that can efficiently use it), but on the other hand they can just "outscore" it to you, guess what choice they will make?
Join the club:
I waited until I checked out the hospital, and the nurse took my information down. For my situation, I have to follow up with specialist. The clinic received my medical information and the referral from the hospital. The clinic also got the typo from the hospital, plus the wrong insurance information, as well as the wrong cell phone number. I was amazed at the wrong insurance (hospital gave them my dental insurance, but I received a notice from my health insurance regarding my hospital admission before I visited the clinic). How funny. When I went back to confirm my appointment a few days later, the clinic said no one correct my name (wtf?).
What a joke. While I was getting admitted into the hospital for a few nights, the nurses had to pair up in order to figure out how to enter data into the system. The program looks like Excel except it isn't. In some cases you have to enter the data in a different column, in some cases you have to enter 0, in some cases you leave it out. The nurses kept saying "oh I remember you have to do this to get around this issue, oh I think you can ignore this option."
When I met with the nurse practitioner the next day, he couldn't log into his system. I told him I work as a DevOps and he was curious about my role. Then he said he has to call the IT support (managed solution) somewhere in Tennessee and all the vendor would say is try again later). Yeah, after meeting 30 minutes he was able to login.
Here is the thing - typo can ruin life, typo can take away money and time for fixing error, can cause divorce and all sorts of other bad things. Insurance, Social Security, government IDs, Diploma, etc.
There is no reason, in my funny but pretty frustrating anecdote, for hospital to run so inefficient, relying on systems built by incompetent people, product dedicated by policy makers or administrators who really are out of touch with real life (they don't use the system).
You know, I am angry, I want to reform hospital software system.