Skip to main content

Data Liquidity


Right from the get-go, I was intrigued by this post which used the phrase "Data Liquidity" since this term is new to me, but I grasp a meaning for it right away. The post points out the importance of interoperability for care continuity and how this impacts value and quality driven care.

As a technologist, ideas and concepts like this always interest me and it represents an area I've dealt with as a software engineer responsible for tying systems together into a coherent whole. I understand the need for continuing technology improvements in this area. But an even more frustrating and worrisome impediment to data liquidity are institutional barriers. I have often run into mazes of siloed data, groundless HIPPA fear-reactions, lack of data management infrastructures, turf wars and other strictly institutional impediments.

I understand that hospitals and healthcare systems are large and complex organizations. But I find that often the data management policies in business, such as financial institutions, are much more well developed.

Think of but a few questions:

  • What data do we have - is it all known and cataloged?
  • Who owns the various data in the organization, what group (or person) is responsible for it?
  • Who has ultimate accountability for the organization’s data?
There is a growing maturity model which can guide the creation of a coherent data management plan. Without the institutional planning and strategy behind trying to achieve data liquidity, the technical portions are the least of the problem.

I would suggest the following series of articles:

Labels:

Comments

Post a Comment

Popular posts from this blog

Let's Not Mess Around with Security on our Personal Systems Either!

Essential Security Practices for Your Personal Systems Ensuring a minimal level of cybersecurity, privacy, and availability on your personal systems means you need to manage the following essential practices. This is a brief overview of recommendations from sources like CISA, NSA, etc., focused on personal laptop, phone, and other systems' security. Anti-virus  I've found you'll get the best anti-virus protection and usability from a paid product - I've always had good luck with Norton labeled products. If you are looking for current vendor offerings see:  https://www.pcmag.com/picks/the-best-antivirus-protection Regardless of whether you choose to use a commercial product or open-source anti-virus tool, it is absolutely something you need to use. This is the minimally needed level of system security. Once installed, ideally, it should be invisible until there's a security problem it can't prevent or solve.   Backups You need to have at least a minimal level of ...
Post a Comment
Read more

RACI, Cybersecurity and NICE Framework

The NICE framework from a RACI point of view The NICE framework ( NIST SP 800-181 rev. 1) established a standard approach for describing cybersecurity work, in order to help stakeholders share a common language and ideally improve how to identify, recruit, develop and retain talent. It breaks down cybersecurity work role categories into: Oversight and Governance; Design and Development; Implementation and Operation; Protection and Defense; Investigation.  Which is very cybersecurity-centric and not related to common tools for project management within companies. Especially smaller enterprises that do not have dedicated people to mange and coordinate cybersecurity needs. A  RACI chart  is   a project management tool used to define and clarify roles and responsibilities within a project team.   It stands for Responsible, Accountable, Consulted, and Informed, and visually represents who is responsible for what, who is accountable for the outcome, who needs to be c...
Post a Comment
Read more

Typescript - It might not be easier, but but it's surely different

Typescript is a statically typed language, that is a superset of JavaScript. I've had the discussions and debates about that aspect of the language. I am all for static typing. Any way my tools can help me be better is alright by me. So I avoid the ' any ' type designation and make sure I have guards on ' unknown ' types, as much as I can.  Any  does not carry any useful type information, while unknown does, and allows it to enforce type checking.  Anything can be assigned to a variable of type unknown , but an unknown value cannot be assigned to variables of other types without explicit type assertion or narrowing. Similarly, no operations are permitted on an unknown value until its type is refined. This behavior ensures type safety and prevents runtime errors. (Refined with help from google). I bring this up because I was arguing with the compiler recently because I'd assumed both made no use on any type information in any circumstance - because I haven't ...
Post a Comment
Read more