ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Scam calls/emails

    IT Discussion
    9
    34
    1.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • travisdh1T
      travisdh1 @Dashrender
      last edited by

      @Dashrender said in Scam calls/emails:

      an FYI in case anyone cares... athenaNet has a single user database for their entire system. So if you work at two different hospital/clinics that both use athenaNet, then you only have one account that accesses both systems...

      So all it really takes is someone that has changed jobs a number of times to companies that all use this same athenaNet?

      DashrenderD 1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender @dafyre
        last edited by

        @dafyre said in Scam calls/emails:

        @Dashrender said in Scam calls/emails:

        @dafyre said in Scam calls/emails:

        @Dashrender said in Scam calls/emails:

        We are going to be doing a report to see if there are any common IPs accessing these three patients.

        Also check and see if the patients are in the same DB?

        They are - all of our patients are in a single DB.. each client of the EHR is in a single DB. I.e. we are a client, and all of our patients are in a single DB.

        I would put a call in to the EHR for sure and tell them what's been happening.

        yup, started the process on Friday - then the line got disconnected.

        I have to call them back today.

        dafyreD 1 Reply Last reply Reply Quote 0
        • DashrenderD
          Dashrender @travisdh1
          last edited by

          @travisdh1 said in Scam calls/emails:

          @Dashrender said in Scam calls/emails:

          an FYI in case anyone cares... athenaNet has a single user database for their entire system. So if you work at two different hospital/clinics that both use athenaNet, then you only have one account that accesses both systems...

          So all it really takes is someone that has changed jobs a number of times to companies that all use this same athenaNet?

          I'm not sure what you are asking?

          There is only one athenaNet. The way they want you to handle users is to never delete them from your system - so in our case we would have somewhere around 50+ people in our system that no longer work here all taking up space in our drop downs because the system has no way of hiding, yet leaving them in, ex-employees. So we say screw that - and delete them. This of course causes us a different problem, once we delete them, we can no longer run reports on them, we have to contact athenaHealth (the company) and have them run the reports for us,

          We'd be happy to leave the users in as no access users, if there was a way to remove them from all of the active user lists - which are used everyday multiple times per day by nearly everyone - as a way to assign tasks to others.

          1 Reply Last reply Reply Quote 0
          • dafyreD
            dafyre @Dashrender
            last edited by

            @Dashrender said in Scam calls/emails:

            @dafyre said in Scam calls/emails:

            @Dashrender said in Scam calls/emails:

            @dafyre said in Scam calls/emails:

            @Dashrender said in Scam calls/emails:

            We are going to be doing a report to see if there are any common IPs accessing these three patients.

            Also check and see if the patients are in the same DB?

            They are - all of our patients are in a single DB.. each client of the EHR is in a single DB. I.e. we are a client, and all of our patients are in a single DB.

            I would put a call in to the EHR for sure and tell them what's been happening.

            yup, started the process on Friday - then the line got disconnected.

            I have to call them back today.

            Hopefully you didn't get disconnected today?

            DashrenderD 1 Reply Last reply Reply Quote 0
            • DashrenderD
              Dashrender @dafyre
              last edited by

              @dafyre said in Scam calls/emails:

              @Dashrender said in Scam calls/emails:

              @dafyre said in Scam calls/emails:

              @Dashrender said in Scam calls/emails:

              @dafyre said in Scam calls/emails:

              @Dashrender said in Scam calls/emails:

              We are going to be doing a report to see if there are any common IPs accessing these three patients.

              Also check and see if the patients are in the same DB?

              They are - all of our patients are in a single DB.. each client of the EHR is in a single DB. I.e. we are a client, and all of our patients are in a single DB.

              I would put a call in to the EHR for sure and tell them what's been happening.

              yup, started the process on Friday - then the line got disconnected.

              I have to call them back today.

              Hopefully you didn't get disconnected today?

              Sadly, the call back didn't happen today.

              scottalanmillerS 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @Dashrender
                last edited by

                @Dashrender said in Scam calls/emails:

                @dafyre said in Scam calls/emails:

                @Dashrender said in Scam calls/emails:

                @dafyre said in Scam calls/emails:

                @Dashrender said in Scam calls/emails:

                @dafyre said in Scam calls/emails:

                @Dashrender said in Scam calls/emails:

                We are going to be doing a report to see if there are any common IPs accessing these three patients.

                Also check and see if the patients are in the same DB?

                They are - all of our patients are in a single DB.. each client of the EHR is in a single DB. I.e. we are a client, and all of our patients are in a single DB.

                I would put a call in to the EHR for sure and tell them what's been happening.

                yup, started the process on Friday - then the line got disconnected.

                I have to call them back today.

                Hopefully you didn't get disconnected today?

                Sadly, the call back didn't happen today.

                Figures.

                DashrenderD 1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender @scottalanmiller
                  last edited by

                  @scottalanmiller said in Scam calls/emails:

                  @Dashrender said in Scam calls/emails:

                  @dafyre said in Scam calls/emails:

                  @Dashrender said in Scam calls/emails:

                  @dafyre said in Scam calls/emails:

                  @Dashrender said in Scam calls/emails:

                  @dafyre said in Scam calls/emails:

                  @Dashrender said in Scam calls/emails:

                  We are going to be doing a report to see if there are any common IPs accessing these three patients.

                  Also check and see if the patients are in the same DB?

                  They are - all of our patients are in a single DB.. each client of the EHR is in a single DB. I.e. we are a client, and all of our patients are in a single DB.

                  I would put a call in to the EHR for sure and tell them what's been happening.

                  yup, started the process on Friday - then the line got disconnected.

                  I have to call them back today.

                  Hopefully you didn't get disconnected today?

                  Sadly, the call back didn't happen today.

                  Figures.

                  Oh, this was on me, not them. I'm just swamped with user issues - training a new user, etc.

                  1 Reply Last reply Reply Quote 0
                  • ObsolesceO
                    Obsolesce
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender
                      last edited by

                      I've made the call back.

                      the EHR vendor say - nope not us - unless we've had such a catastrophic hack that we can't detect it in our logs.

                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                      • scottalanmillerS
                        scottalanmiller @Dashrender
                        last edited by

                        @Dashrender said in Scam calls/emails:

                        the EHR vendor say - nope not us - unless we've had such a catastrophic hack that we can't detect it in our logs.

                        "Not in our logs" is a pretty weak defense of not having been hacked.

                        JaredBuschJ 1 Reply Last reply Reply Quote 1
                        • JaredBuschJ
                          JaredBusch @scottalanmiller
                          last edited by JaredBusch

                          @scottalanmiller said in Scam calls/emails:

                          @Dashrender said in Scam calls/emails:

                          the EHR vendor say - nope not us - unless we've had such a catastrophic hack that we can't detect it in our logs.

                          "Not in our logs" is a pretty weak defense of not having been hacked.

                          While true, I would also lean towards his network being infected and him not knowing it, over a large EHR vendor.

                          We also know (assume as a smaller SMB) he has no SEIM to give him information about the state of his network.

                          scottalanmillerS DashrenderD 2 Replies Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @JaredBusch
                            last edited by

                            @JaredBusch said in Scam calls/emails:

                            While true, I would also lean towards his network being infected and him not knowing it, over a large EHR vendor.

                            Agreed. Way more likely

                            1 Reply Last reply Reply Quote 0
                            • DashrenderD
                              Dashrender @JaredBusch
                              last edited by

                              @JaredBusch said in Scam calls/emails:

                              @scottalanmiller said in Scam calls/emails:

                              @Dashrender said in Scam calls/emails:

                              the EHR vendor say - nope not us - unless we've had such a catastrophic hack that we can't detect it in our logs.

                              "Not in our logs" is a pretty weak defense of not having been hacked.

                              While true, I would also lean towards his network being infected and him not knowing it, over a large EHR vendor.

                              We also know (assume as a smaller SMB) he has no SEIM to give him information about the state of his network.

                              I definitely agree with this. The odd thing is we can't find a correlation between these incidents. Not the same doc, not the same staff, not the same computer.

                              scottalanmillerS 1 Reply Last reply Reply Quote 0
                              • scottalanmillerS
                                scottalanmiller @Dashrender
                                last edited by

                                @Dashrender said in Scam calls/emails:

                                @JaredBusch said in Scam calls/emails:

                                @scottalanmiller said in Scam calls/emails:

                                @Dashrender said in Scam calls/emails:

                                the EHR vendor say - nope not us - unless we've had such a catastrophic hack that we can't detect it in our logs.

                                "Not in our logs" is a pretty weak defense of not having been hacked.

                                While true, I would also lean towards his network being infected and him not knowing it, over a large EHR vendor.

                                We also know (assume as a smaller SMB) he has no SEIM to give him information about the state of his network.

                                I definitely agree with this. The odd thing is we can't find a correlation between these incidents. Not the same doc, not the same staff, not the same computer.

                                Same network, though.

                                1 Reply Last reply Reply Quote 0
                                • 1
                                • 2
                                • 2 / 2
                                • First post
                                  Last post