Scott Olson

Aspiring to Create, Explore, and Discover | He/Him (views are my own)

[Scott Olson @scottolsonjr]

Not doing well enough is not the same as not being good enough. Your value is not based on your current competence but simply in your being.

[Scott Olson @scottolsonjr]

@healthapiguy Good arguments. I totally agree on the gaps and opportunities and am hoping that we continue to see efforts in that space. We need to get beyond recruiting patients simply to populate data warehouses and provide value to them

[Scott Olson @scottolsonjr]

@healthapiguy Does this opinion carry over to personal budgeting apps? Seems an odd recommendation to suggest patients are better off managing their health across disparate provider/payer portals. Unless that’s the point? “Don’t just aggregate. Do something helpful.” E.g., make a budget, etc.

[Scott Olson @scottolsonjr]

@tomherzog Good stuff. What do you do when the meetings or time blocks are misaligned with your goals? You mention pivoting the goals later. Anything else?

[Auschwitz Memorial @AuschwitzMuseum]

For the upcoming 80th anniversary of the liberation of Auschwitz, we hope to reach 2 million followers.

Achieving this goal would not only be a tribute to the memory of Victims but also crucial support for our educational mission.

Your engagement is vital. Everyone can help.

[Scott Olson @scottolsonjr]

@healthapiguy @sequoiaproject Ha I meant not sure whether the QHINs would be permitted to publish publicly. I imagine they could for their own participants at least since they have to facilitate the discovery and exchange for them anyway.

[Scott Olson @scottolsonjr]

@healthapiguy Yeah the first one would correspond to the RCE. I wonder if @sequoiaproject has anything like this in the works? I’m sure any of the QHINs would be allowed to publish something like this…at least publicly.

[Scott Olson @scottolsonjr]

@kdmertz @healthapiguy I thought all or most of the QHINs had this kind of press release as part of their designation process. How would you like to see the list be accessible post-designation (assuming you are not already a participant or sub-participant in one of the QHINs)?

[Scott Olson @scottolsonjr]

@davidfowl I started learning their CDK last year and never want to edit a CloudFormation yaml file directly ever again haha

[Office of the National Coordinator for Health IT @ONC_HealthIT]

Our new USCDI+ platform for organizing and building out various USCDI+ datasets is live! We are also seeking public comments and submission of data elements for public health. Read more via the Buzz Blog: https://t.co/I9vI5mgvUz

[dmarcian @dmarcian]

We've created this guide to help organizations of all sizes prepare for the Google and Yahoo #DMARC requirement coming in February 2024. Let us know if you have any questions! #dmarcian https://t.co/Mlo5qnXeKg

[Office of the National Coordinator for Health IT @ONC_HealthIT]

#TEFCA updates! The Common Agreement has been updated to Version 1.1 in preparation for data sharing on TEFCA, and multiple candidate QHIN organizations are working to complete onboarding and go-live by the end of 2023! https://t.co/wD4iyKyYbG

[Eric Erhardt @eehardt]

If you are interested in learning how to ensure your .NET library works with native AOT, check out this post.

https://t.co/eJMvxepjgf

[Netsmart @NetsmartTech]

CONNECTIONS2024 is headed to Texas! 🤠 Mark your calendars for Sept. 3rd-6th. #CONN24 promises an incredible experience, offering valuable learning opportunities & networking with industry professionals. Stay tuned for registration details coming in the new year. See you there!

[Tess @TessFerrandez]

I often hear "minimal APIs are just for toy apps" - I use them all the time and love them, for big and small projects, so I decided to jolt down some quick notes about how we organize our minimal APIs to make them maintainable and testable https://t.co/vMOWrya8Xm

[Osaretin Victor Asemota @asemota]

Three things happened to me today that put starting businesses in Africa into new perspective.

1. We had to go find a good doctor at a remote location because of a referral. He was expensive not just because he was good be because he was isolated and the place wasn't busy.

[Scott Olson @scottolsonjr]

@healthapiguy Hopefully we’ll see variability reduce over time in authZ/authN as well as FHIR operation and payload/profile conformance. Thanks!

[Scott Olson @scottolsonjr]

@healthapiguy Ah got it. I can see that. Thanks for the clarification. That provides additional context for why SMART can be helpful here:

1) fhirUser claim on ID Token (e.g., Patient or Practitioner)
2) plus, launch context in the token response

[Scott Olson @scottolsonjr]

@healthapiguy This one I find intriguing.
1) the access token is between the auth server and resource server so it shouldn’t matter to the client how patient ID is used there (or not)
2) a patient ID in an ID Token would only make sense in Patient Access describing the authenticated user