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:

Comments

Popular posts from this blog

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...

Threat Modeling Manifesto

Secure Your Code with Threat Modeling As a software developer, security should be a top priority. By proactively identifying and addressing potential vulnerabilities, you can significantly reduce the risk of breaches and data loss. What is Threat Modeling?   Threat modeling is a systematic approach to identifying, assessing, and mitigating security threats. It involves looking at your system from a hacker's perspective to uncover weaknesses and devise strategies to protect against attacks. See the  OWASP Cheat Sheet   Why is Threat Modeling Important? Proactive Security: By anticipating potential threats, you can take steps to prevent them. Risk Mitigation: Identify and address vulnerabilities before they can be exploited. Regulatory Compliance: Adhere to industry standards and regulations. Enhanced Security Posture: Strengthen your overall security posture. How to Get Started with Threat Modeling   The Threat Modeling Manifesto provides a valuable framewor...

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...