The Midland Mainline beyond Moore Lane, Loughborough, January 2025

#photography #ukphotography #landscapephotography #loughborough #uktopographicmar25 #emr #nikon

https://www.saal-digital.net/profiles/wim_van_mierlo/

Emerald Resources ( #EMR ) has released " Emerald Now Debt Free " on Wed 02 Apr at 08:48 AEST #ESG #Gold #Australia #media #live
https://grafa.com/asset/emerald-resources-nl-6841-emr.asx?utm_source=asxmktsensitive&utm_medium=mastodon&utm_campaign=emr.asx

How delightful.... not.

https://www.cyclingeu.com/544673/birmingham-derby-stoke-on-trent-circular-route/ Birmingham – Derby – Stoke-on-Trent | Circular Route #Bicycling #BicyclingUK #BicyclingUnitedKingdom #Biking #BikingUK #BikingUnitedKingdom #Birmingham #CircularRoute #crosscountry #Cycling #CyclingBurtonUponTrentUK #CyclingUk #CyclingUnitedKingdom #derby #EastMidlandsRailway #EMR #StokeOnTrent #UK #UKTrains #UnitedKingdom

Nottingham Station, March 2024

#photography #ukphotography #nottingham #station #railwaystation #EMR #nikon #newtopographics

https://www.saal-digital.net/profiles/wim_van_mierlo/

Since December 26, I have been working with the team for a major medical #EMR portal third part imaging portal about a #security and #HIPAA breach I discovered. This portal has tens of millions of medical patients from several thousand hospitals, almost half the inpatient and outpatient patient base in the US. They run in house and external medical operations. Not hyperbole.

On the patient side, essentially, portal A, the main EMR portal, allows others to share their medical chart with you, even letting you manage their medical records from your account.

Recently, they hooked up with a third-party imaging portal, Portal B.

If you want to see your imaging, x-rays, CTs, etc, you have to click to go out to Portal B, automatically logged in.

The first time you view medical imaging; it creates the third-party Portal B user account.

Well, a family member shared their medical chart account with me with full access on Portal A a long time ago. This past week they were hospitalized and had some imaging.

I logged into my EMR chart at Portal A, I changed to their view and then clicked to view their imaging which led the third part Portal B for the first time and it created the new, first-time account, without any intervention from me, by populating data from the main Portal A EMR site.

Because I had never done the Portal B setup by viewing my imaging first, Portal B created my new account with my Portal A credentials and because I was doing it from their view from within my account, mixed up my data and demographics and my family members when it was created. This actually gave them the imaging account with my credentials.

On the security side, it also shared with them every person that entrusted me with their medical information by sharing with me, and added them to their account, partially with my credentials. So, now they could see my trusted sharers imagining, without their consent or knowledge.

I am not confident they are really fixing it. So far, they deleted the erroneous account and then told me to log in to Portal A, go to my imaging and click view imaging and then recreate my account to clear that mess up.

I plan on filing notice with Portal A and HHS OCR (Office of Civil Rights) to make sure they aren't just doing a Band-Aid fix. They need to pull the 3rd-party access until it is resolved. I don't expect to get an autopsy of how they worked on a fix, what the issues are, etc, but both Portal A and HHS needs to make sure there isn't a big security and HIPAA breach out there waiting to be exploited. #Infosec. I am keeping all emails and records. That's another thing, why am I involved at this point.

I believe they are working on it, and this discovery made a significant headache for them and probably ruined their New Years plans. I hope, at least, they are taking this as seriously as they should be.

Because this EMR runs in thousands of hospitals with tens of millions of patients, somebody big needs to look into this. As I said above, this is not hyperbole.

#EMR don’t seem to care very much about their trains, so filthy on the outside, has the train cleaner broken or can they not be arsed to clean them.

Difficult to have pride in your trains when they look like they’ve just popped out of the sewer

Got recommended a job working on HL7.

I have resolved HL7 transmission issues before between the on-prem software and associated storage, a caching server at another site, the intermediary interface that routes to cloud EHR... But man what a mess, even with vendors on the call.

BREAKING: #Epic, the largest electronic health records company in the US, which holds data on over 75% of Americans, sued over monopolistic antitrust practices by Particle Health

more @STAT
#EHR #EMR #medicine #health #monopoly #antitrust

https://www.statnews.com/2024/09/23/epic-lawsuit-particle-health-alleged-monopolistic-practices-ehr/

18th September:
Work:
2V38 07:39 #Reigate to #DorkingDeepdene: On time:
https://www.realtimetrains.co.uk/service/gb-nr:G45477/2024-09-18/detailed#allox_id=0

1O80 18:29 #DorkingDeepdene to #Reigate: 3 minutes late.
https://www.realtimetrains.co.uk/service/gb-nr:G44937/2024-09-18/detailed#allox_id=0

Daily delay (#GWR): 3 minutes.

26 #Southern On time.
36 #GWR On time.
6 #SWR On time.
1 #LondonOverground On time.
4 #Thameslink On time.
2 #Southeastern On time
1 #ElizabethLine On time
Overall On time 78 / 134 trains.

#GWR delays: 2 hours & 16 minutes.
#Thameslink delays: 3 minutes.
#Southern delays: 1 hour.
#EMR

I’m working on deploying #spark on my first #EMR cluster on #AWS and running into the same old quandary: I have a small repo with my #python tools and sample data files, and I try to always make things repeatable - what’s the best way to create a CI/CD-based #deployment for AWS?

I’ve used CloudFormation, I started reading about CDK but hooboy the layers and abstractions…

#ansible or #terraform are also possibilities but right now I’m trying to keep it simple…

So my next steps with #spark and #python will probably happen on AWS #EMR but this article really helped my get a #dockercompose based spark cluster up and running locally, and get #jupyterlab working enough to start actually interacting with Spark.

https://karlchris.github.io/data-engineering/projects/spark-docker/#running-ml-models

emr
#kamloops #train #graffiti #art
#emr