healthcarereimagined

Envisioning healthcare for the 21st century

  • About
  • Economics

Air Force’s Outgoing 1st Chief Architect Officer Offers 4 Steps for Overcoming Bureaucracy – Air Force Magazine

Posted by timmreardon on 04/19/2022
Posted in: Uncategorized. Leave a comment

April 19, 2022 | By Greg Hadley

Preston Dunlap, the Department of the Air Force’s first-ever chief architect officer, is set to leave the Pentagon in the coming weeks, he confirmed in a lengthy LinkedIn post on April 18—and he has a long list of recommendations for those coming after him on how to combat Defense Department bureaucracy.

Dunlap’s departure, first reported by Bloomberg, marks the latest exit by a high-ranking Air Force official tasked with modernizing the department’s approach to software and technology. In September 2021, Nicolas M. Chaillan, the first-ever chief software officer of the Air Force, announced his resignation, also on LinkedIn and also offering a candid assessment of the challenges facing DAF.

Dunlap first came to the Air Force in 2019, primarily tasked with overseeing the development and organization of the Advanced Battle Management System, the Air Force’s contribution to joint all-domain command and control—the so-called military Internet of Things that will connect sensors and shooters into one massive network.

Under Dunlap, progress on ABMS proceeded with numerous experiments. Dunlap also oversaw the development of an “integrated warfighting network” to allow small teams of Airmen serving in far-flung locations to use their work laptops on deployments.

“It’s been my honor to help our nation get desperately needed technology into the hands of our service members who place their lives on the line every day,” Dunlap wrote on LinkedIn. “Some of that technology was previously unimaginable before we developed new capabilities, and at other times it was previously unattainable—available commercially, yet beyond DOD’s grasp.”

Initially, Dunlap wrote, he signed on for two years in the Pentagon, before agreeing to extend his stay for a third year. Now, as he departs, he is joining Chaillan in pointing out the DOD’s shortcomings when it comes to innovation and pushing the department to revolutionize its approach, especially for adopting new technologies, so that it can, in his words, “defy gravity.”

“Not surprisingly to anyone who has worked for or with the government before, I arrived to find no budget, no authority, no alignment of vision, no people, no computers, no networks, a leaky ceiling, even a broken curtain,” Dunlap wrote.

In looking to break through bureaucracy, Dunlap wrote, he followed four key steps that he urged his successor to follow: shock the system, flip the acquisition script, just deliver already, and slay the valley of death and scale.

In doing so, he said, he sought to operate more like SpaceX, the aerospace company founded by Elon Musk that has earned plaudits for its fast-moving, innovative practices.

“By the time the government manages to produce something, it is too often obsolete; no business would ever survive this way, nor should it. Following a commercial approach, just like SpaceX, allowed me to accomplish a number of ‘firsts’ in DOD in under two years,” Dunlap wrote.

Among those firsts, Dunlap referenced the integration of artificial intelligence into military kill chains, interoperability of data and communications across different satellites and aircraft, the deployment of zero trust architecture, and the promotion of security in software development, known as DevSecOps.

In addition, Dunlap argued for a “reformatting” of the Pentagon’s acquisition enterprise, an oft-criticized process seen by many as out-dated and antiquated. By leveraging commercial technologies, shifting focus to outcomes instead of detailed requirements, putting more investments in outside innovators, and pushing forward with a concerted, rapid pace, the Pentagon can start to “regrow its thinning technological edge,” Dunlap wrote.

In order to help develop innovation and progress, Dunlap also pushed for flexibility—both in how the department works and connects, and in how it develops new systems. In particular, he argued for open systems and open architectures to allow new systems to rapidly adapt to and integrate new capabilities as they are developed, pointing to the B-21 Raider and Next-Generation Air Dominanceprograms as examples of that approach.

“We should never be satisfied,” Dunlap closed by writing. “We need this kind of progress at scale now, not tomorrow. So let’s be careful to not…

  • “Lull ourselves into complacency, when we should be running on all cylinders.
  • “Do things the same way, when we should be doing things better.
  • “Distract ourselves with process, when we should be focused on delivering product.
  • “Compete with each other, when we should be competing with China.
  • “Defend our turf, when we should be defending our country.
  • “Focus on input metrics, when we should be focused on output metrics.
  • “Buy the same things, when we should be investing in what we need.
  • “Be comfortable with the way things are, when we should be fighting for the way things should be.”

Dunlap’s departure comes at a seeming inflection point for the ABMS program he was tasked with overseeing. Air Force Secretary Frank Kendall has indicated he wants to take a different approach to the program, focusing more on specific operational impacts delivered quickly and less on experiments showing advanced capabilities.

“We can’t invest in everything, and we shouldn’t invest in improvements that don’t have clear operational benefit,” Kendall said March 3 at the AFA Warfare Symposium in Orlando, Fla.. “We must be more focused on specific things with measurable value and operational impact.”

As part of that approach, Kendall has made it one of his organizational imperatives to more fully define the goals and impacts the ABMS program is going for.

Article link: https://www.airforcemag.com/air-force-first-chief-architect-officer-preston-dunlap-set-to-exit/

Ethics and AI: 3 Conversations Companies Need to Have – HBR

Posted by timmreardon on 04/19/2022
Posted in: Uncategorized. Leave a comment

by Reid Blackman & Beena Ammanath

March 21, 2022

Summary.   

While concerns about AI and ethical violations have become common in companies, turning these anxieties into actionable conversations can be tough. With the complexities of machine learning, ethics, and of their points of intersection, there are no quick fixes, and conversations around these issues can feel nebulous and abstract. Getting to the desired outcomes requires learning to talk about these issues differently. First, companies must decide who needs to be part of these conversations. Then, they should: 1) define their organization’s ethical standards for AI, 2) identify the gaps between where you are now and what your standards call for, and 3) understand the complex sources of the problems and operationalize solutions.

Over the past several years, concerns around AI ethics have gone mainstream. The concerns, and the outcomes everyone wants to avoid, are largely agreed upon and well documented. No one wants to push out discriminatory or biased AI. No one wants to be the object of a lawsuit or regulatory investigation for violations of privacy. But once we’ve all agreed that biased, black box, privacy-violating AI is bad, where do we go from here? The question most every senior leader asks is: How do we take action to mitigate those ethical risks?

Acting quickly to address concerns is admirable, but with the complexities of machine learning, ethics, and of their points of intersection, there are no quick fixes. To implement, scale, and maintain effective AI ethical risk mitigation strategies, companies should begin with a deep understanding of the problems they’re trying to solve. A challenge, however, is that conversations about AI ethics can feel nebulous. The first step, then, should consist of learning how to talk about it in concrete, actionable ways. Here’s how you can set the table to have AI ethics conversations in a way that can make next steps clear.

Who Needs to Be Involved?

We recommend assembling a senior-level working group that is responsible for driving AI ethics in your organization. They should have the right skills, experience, and knowledge such that the conversations are well-informed about the business needs, technical capacities, and operational know-how. At a minimum, we recommend involving four kinds of people: technologists, legal/compliance experts, ethicists, and business leaders who understand the problems you’re trying to solve for using AI. Their collective goal is to understand the sources of ethical risks generally, for the industry of which they are members, and for their particular company. After all, there are no good solutions without a deep understanding of the problem itself and the potential obstacles for proposed solutions.

You need the technologist to assess what is technologically feasible, not only at a per product level but also at an organizational level. That is because, in part, various ethical risk mitigation plans require different tech tools and skills. Knowing where your organization is from a technological perspective can be essential to mapping out how to identify and close the biggest gaps.

Legal and compliance experts are there to help ensure that any new risk mitigation plan is compatible and not redundant with existing risk mitigation practices. Legal issues loom particularly large in light of the fact that it’s neither clear how existing laws and regulations bear on new technologies, nor what new regulations or laws are coming down the pipeline.

Ethicists are there to help ensure a systematic and thorough investigation into the ethical and reputational risks you should attend to, not only by virtue of developing and procuring AI, but also those risks that are particular to your industry and/or your organization. Their importance is particularly relevant because compliance with outdated regulations does not ensure the ethical and reputational safety of your organization.

Finally, business leaders should help ensure that all risk is mitigated in a way that is compatible with business necessities and goals. Zero risk is an impossibility so long as anyone does anything. But unnecessary risk is a threat to the bottom line, and risk mitigation strategies also should be chosen with an eye towards what is economically feasible.

Three Conversations to Push Things Forward

Once the team is in place, here are three crucial conversations to have. One conversation concerns coming to a shared understanding of what goals an AI ethical risk program should be striving for. The second conversation concerns identifying gaps between where the organization is now and where it wants to be. The third conversation is aimed at understanding the sources of those gaps so that they are comprehensively and effectively addressed.

1) Define your organization’s ethical standard for AI.

Any conversation should recognize that legal compliance (e.g. anti-discrimination law) and regulatory compliance (with, say, GDPR and/or CCPA) are table stakes. The question to address is: Given that the set of ethical risks is not identical to the set of legal/regulatory risks, what do we identify as the ethical risks for our industry/organization and where do we stand on them?

There are a lot of tough questions that need answers here. For instance, what, by your organization’s lights, counts as a discriminatory model? Suppose, for instance, your AI hiring software discriminates against women but it discriminates lessthan they’ve been historically discriminated against. Is your benchmark for sufficiently unbiased “better than humans have done in the last 10 years”? Or is there some other benchmark you think is appropriate? Those in the self-driving car sector know this question well: “Do we deploy self-driving cars at scale when they are better than the average human driver or when they are at least as good as (or better than) our best human drivers?”

Similar questions arise in the context of black box models. Where does your organization stand on explainability? Are there cases in which you find using a black box acceptable (e.g. so long as it tests well against your chosen benchmark)? What are the criteria for determining whether an AI with explainable outputs is otiose, a nice-to-have, or a need-to-have?

Going deep on these questions allows you to develop frameworks and tools for your product teams and the executives who green light deployment of the product. For instance, you may decide that every product must go through an ethical risk due diligence process before being deployed or even at the earliest stages of product design. You may also settle on guidelines regarding when, if at any time, black box models may be used. Getting to a point where you can articulate what the minimum ethical standards are that all AI must meet is a good sign that progress has been made. They are also important for gaining the trust of customers and clients, and they demonstrate your due diligence has been performed should regulators investigate whether your organization has deployed a discriminatory model.

2) Identify the gaps between where you are now and what your standards call for.

There are various technical “solutions” or “fixes” to AI ethics problems. A number of software products from big tech to startups to non-profits help data scientists apply quantitative metrics of fairness to their model outputs. Tools like LIME and SHAP aid data scientists in explaining how outputs are arrived at in the first place. But virtually no one thinks these technical solutions, or any technological solution for that matter, will sufficiently mitigate the ethical risk and transform your organization into one that meets its AI ethics standards.

Your AI ethics team should determine where their respective limits are and how their skills and knowledge can complement each other. This means asking:

  1. What, exactly, is the risk we’re trying to mitigate?
  2. How does software/quantitative analysis help us mitigate that risk?
  3. What gaps do the software/quantitative analyses leave?
  4. What kinds of qualitative assessments do we need to make, when do we need to make them, on what basis do we make them, and who should make them, so that those gaps are appropriately filled?

These conversations should also include a crucial piece that is standardly left out: what level of technological maturity is needed to satisfy (some) ethical demands (e.g., whether you have the technological capacity to provide explanations that are needed in the context of deep neural networks). Having productive conversations about what AI ethical risk management goals are achievable requires keeping an eye on what is technologically feasible for your organization.

Answers to these questions can provide clear guidance on next steps: assess what quantitative solutions can be dovetailed with existing practices by product teams, assessing the organization’s capacity for the qualitative assessments, and assessing how, in your organization, these things can be married effectively and seamlessly.

3) Understand the complex sources of the problems and operationalize solutions.

Many conversations around bias in AI start with giving examples and immediately talking about “biased data sets.” Sometimes this will slide into talk about “implicit bias” or “unconscious bias,” which are terms borrowed from psychology that lack a clear and direct application to “biased data sets.” But it’s not enough to say, “the models are trained on biased data sets” or “the AI reflects our historical societal discriminatory actions and policies.”

The issue isn’t that these things aren’t (sometimes, often) true; it’s that it cannot be the whole picture. Understanding bias in AI requires, for instance, talking about the various sources of discriminatory outputs. That can be the result of the training data; but how, exactly, those data sets can be biased is important, if for no other reason than that how they are biased informs how you determine the optimal bias-mitigation strategy. Other issues abound: how inputs are weighted, where thresholds are set, and what objective function is chosen. In short, the conversation around discriminatory algorithms has to go deep around the sourcesof the problem and how those sources connect to various risk-mitigation strategies.

. . .

Productive conversations on ethics should go deeper than broad stroke examples descried by specialists and non-specialists alike. Your organization needs the right people at the table so that its standards can be defined and deepened. Your organization should fruitfully marry its quantitative and qualitative approaches to ethical risk mitigation so it can close the gaps between where it is now and where it wants it to be. And it should appreciate the complexity of the sources of its AI ethical risks. At the end of the day, AI ethical risk isn’t nebulous or theoretical. It’s concrete. And it deserves and requires a level attention that goes well beyond the repetition of scary headlines.

Article link: https://hbr.org/2022/03/ethics-and-ai-3-conversations-companies-need-to-be-having?

  • Reid Blackman, Ph.D., is the author of “Ethical Machines: Your concise guide to totally unbiased, transparent, and respectful AI” (Harvard Business Review Press, July 2022) and Founder and CEO of Virtue, an ethical risk consultancy. He is also a Senior Advisor to the Deloitte AI Institute, previously served on Ernst & Young’s AI Advisory Board, and volunteers as the Chief Ethics Officer to the non-profit Government Blockchain Association. Previously, Reid was a professor of philosophy at Colgate University and the University of North Carolina, Chapel Hill.
  • BABeena Ammanath is the Executive Director of the global Deloitte AI Institute, author of the book “Trustworthy AI,” founder of the non-profit Humans For AI, and also leads Trustworthy and Ethical Tech for Deloitte. She is an award-winning senior executive with extensive global experience in AI and digital transformation, spanning across e-commerce, finance, marketing, telecom, retail, software products, services and industrial domains with companies such as HPE, GE, Thomson Reuters, British Telecom, Bank of America, and e*trade.

Monthly Tech Talk for Industry – CyberBytes Foundation

Posted by timmreardon on 04/18/2022
Posted in: Uncategorized. Leave a comment

Our monthly Marine Corps Systems Command Tech Talk for Industry and the Acquisition community is 3 days away!

Hosted by the CTO of MARCORSYSCOM Luis E. Velazquez.
Date and Time: Thursday (4/21) @1300
Location: #QuanticoCyberHub – 1010 Corporate Dr. Stafford, Va 22554

The #MARCORSYSCOM Tech Talk is open to everyone and we strongly encourage all from #government and #industry to attend to see the technologies showcased that our United States Marine Corps is exploring to help the war fighting capabilities of our troops.

This month will highlight the technologies from the following organizations:

– Marine Corps Systems Command
– Cubic Mission & Performance Solutions
– 4 Horsemen Solutions™
– Epic Games
– Defense Innovation Unit (DIU)
– Perspective
– CORAS
– Checkmarx

community #tech #engineering #marine #TechTalk #Technology #TechLeaders #CTO #MarineCorps #DoD #acquisition #Data #Analytics #Showcase #Demos

Matthew Weaver | ♦️Amanda S. | Joel Scharlat | Kaleb Hunter | Dr Aaron J Miller | Jonathan Payton | John Barker | Matthew Wiltshire | Cesar Nader (USMC, Ret.) | Brooke B. | Luis E. Velazquez | Jourdan Davis | Gabriella Mathieu

MHS GENESIS Now Deployed at 66 of 138 Military Hospital and Clinic Commands

Posted by timmreardon on 04/17/2022
Posted in: Uncategorized. Leave a comment

“MHS GENESIS is now live!” proclaimed Navy Captain Reg Ewing, commander of the Naval Medical Center Camp LejeuneNaval Medical Center Camp Lejeune webpage in North Carolina, on Saturday, March 19. 

And with that 14 new military hospital and clinic commands across Waves BRAGG and HOOD deployed MHS GENESIS, the new federal electronic health record. 

MHS GENESIS replaces several Department of Defense legacy health care systems supporting the availability of electronic health records at 66 military hospital and clinic commands across the United States. 

The latest waves added hospitals and clinics at Ft. Bragg, Seymour Johnson Air Force Base, Marine Corps Base Camp Lejeune, Marine Corps Air Station Cherry Point, Second Dental Battalion, Ft. Hood, Ft. Sill, Ft. Polk, Barksdale AB, Little Rock AFB, Tinker AFB, Altus AFB, Vance AFB, and Naval Air Station Belle Chase. 

This new electronic health record will integrate beneficiary data to healthcare teams across the DOD, Department of Veterans Affairs and the Department of Homeland Security’ U.S. Coast Guard, as all are using the same system. 

Army Col. Aristotle Vaseliades, hospital commander at the Bayne-Jones Army Community HospitalBayne-Jones Army Community Hospital website at Fort Polk in Louisiana, explained that the full transition will take some time as BJACH staff and providers learn new workflows. 

“On Saturday morning a mother in labor arrived at our Labor, Delivery and Postpartum department, we had a patient in our mixed medical surgical department and normal weekend trauma and emergencies gave our staff the opportunity to use the system live in real time,” he said. “As we prepared for “go live” we also invited patients to come through our outpatient clinics. We had patients arrive at different departments for periodic health assessments, knee pain, immunizations, pharmacy and lab work. It went pretty smoothly minus a few bumps in the road which our information management department immediately fixed.” 

At the Carl R. Darnall Army Medical CenterCarl R. Darnall Army Medical Center website at Fort Hood in Texas, Arrington, clinical workflow analyst, added her take on the new system. “[MHS] GENESIS is putting every system together, and staff members will not have to switch between multiple programs, which will make it easy for hospital staff to serve our beneficiaries better.” 

Army Col. Christopher Jarvis, Womack Army Medical CenterWomack Army Medical Center webpage commander, noted the hard work and dedication it took to get WAMC ready to deploy.

“We trained over 4,000 users within the hospital, outlying clinics, and operational forces over a five- month period. We received millions of dollars of new equipment–enough to fill up a warehouse–and issued it to thousands of users across Fort Bragg,” Jarvis said. “The training of personnel and administration of new equipment alone, required thousands of manpower hours and an inordinate amount of coordination and resources.” 

Army Lt. Col. Daniel Cash, deputy commander for clinical services at BJACH, explained how rebuilding patient records is the biggest challenge in the deployment of MHS GENESIS. 

“Not all information from the legacy systems is pulled over into MHS GENESIS so we are updating medical records at each patient’s initial visit post ‘go live’,” he said. “Patients and beneficiaries should come to their first appointments prepared to give a little historical background on their medical history in order to populate the new system.” 

MHS GENESIS enables the application of standardized workflows, integrated healthcare delivery, and data standards for the improved and secure electronic exchange of medical and patient data. 

By the end of next year, MHS GENESIS will be deployed across the entire enterprise providing for all 9.6 million beneficiaries.

Article link: https://health.mil/News/Articles/2022/04/08/MHS-GENESIS-Now-Deployed-at-66-of-138-MTF-Commands

Different Types of Edge Computing – NVIDIA

Posted by timmreardon on 04/16/2022
Posted in: Uncategorized. Leave a comment

By Amanda Saunders

Discuss (0) Share

Tags: CloudXR, featured, Metropolis, technical walkthrough

Many organizations have started their journey towards edge computing to take advantage of data produced at the edge. The definition of edge computing is quite broad. Simply stated, it is moving compute power physically closer to where data is generated, usually an edge device or IoT sensor.

This encompasses far edge scenarios like mobile devices and smart sensors, as well as more near edge use cases like micro-data centers and remote office computing. In fact, this definition is so broad that it is often talked about as anything outside of the cloud or main data center. 

With such a wide variety of use cases, it is important to understand the different types of edge computing and how they are being used by organizations today. 

Provider edge

The provider edge is a network of computing resources accessed by the Internet. It is mainly used for delivering services from telcos, service providers, media companies, or other content delivery network (CDN) operators. Examples of use cases include content delivery, online gaming​, and AI as a service (AIaaS). 

One key example of the provider edge that is expected to grow rapidly is augmented reality (AR) and virtual reality (VR). Service providers want to find ways to deliver these use cases, commonly known as eXtended Reality (XR), from the cloud to end user edge systems. 

In late 2021, Google partnered with NVIDIA to deliver high-quality XR streaming from Google Cloud NVIDIA RTX powered servers, to lightweight mobile XR displays. By using NVIDIA CloudXR to stream from the provider edge, users can securely access data from the cloud at any time and easily share high-fidelity, full graphics immersive XR experiences with other teams or customers.

Enterprise edge

The enterprise edge is an extension of the enterprise data center, consisting of things like data centers at remote office sites, micro-data centers, or even racks of servers sitting in a compute closet on a factory floor. This environment is generally owned and operated by IT as they would a traditional centralized data center, though there may be space or power limitations at the enterprise edge that change the design of these environments.

Retailers can use edge AI across their business for frictionless shopping, in store analytics as well as supply chain optimization.

Figure 1. Enterprises across all industries use edge AI to drive more intelligent use cases on site.

Looking at examples of the enterprise edge, you can see workloads like intelligent warehouses and fulfillment centers. Improved efficiency and automation of these environments requires robust information, data, and operational technologies to enable AI solutions like real-time product recognition.

Kinetic Vision helps customers build AI for these enterprise edge environments using a digital twin, or photorealistic virtual version, of a fulfillment or distribution center to train and optimize a classification model that is then deployed in the real world. This powers faster, more agile product inspections, and order fulfillments.

Industrial edge

The industrial edge, sometimes called the far edge, generally has smaller compute instances that can be one or two small, ruggedized servers or even embedded systems deployed outside of any sort of data center environment.

Industrial edge use cases include robotics, autonomous checkout, smart city capabilities like traffic control, and intelligent devices. These use cases run entirely outside of the normal data center structure, which means there are a number of unique challenges for space, cooling, security, and management.

BMW is leading the way with industrial edge by adopting robotics to redefine their factory logistics. Using different robots for parts of the process, these robots take boxes of raw parts on the line and transport them to shelves to await production. They are then taken to manufacturing, and finally returned back to the supply area when empty.

Robotics use cases require compute power both in the autonomous machine itself, as well as compute systems that sit on the factory floor. To optimize the efficiency and accelerate deployment of these solutions, NVIDIA introduced the NVIDIA Isaac Autonomous Mobile Robot (AMR) platform.

Accelerating edge computing

Each of these edge computing scenarios has different requirements, benefits, and deployment challenges. To understand if your use case would benefit from edge computing, download the Considerations for Deploying AI at the Edge whitepaper

Article link: https://developer.nvidia.com/blog/different-types-of-edge-computing/?

Sign up for Edge AI News to stay up to date with the latest trends, customers use cases, and technical walkthroughs.

About the Authors

About Amanda Saunders 
Amanda Saunders leads product marketing for Edge AI in edge and enterprise computing solutions group at NVIDIA. She brings to life edge computing solutions that bring intelligence to hospitals, stores, warehouses, factories, and more. In addition to working on edge solutions, Amanda has held sales and marketing roles at NVIDIA working with AI, data science, virtual GPU, and many different industries.

View all posts by Amanda Saunders

Building a Cybersecurity Mesh Architecture in the Real World – Dark Reading

Posted by timmreardon on 04/13/2022
Posted in: Uncategorized. Leave a comment


Yash Prakash
Chief Strategy Officer, Saviynt

April 12, 2022

Like zero trust, the cybersecurity mesh re-envisions the perimeter at the identity layer and centers upon unifying disparate security tools into a single, interoperable ecosystem.

The past two years’ events have taught us all just how important it is to stay agile and flexible. We’ve experienced a more challenging threat landscape as well as expanding attack surfaces. These challenges have come with accelerated cloud transformation and the dissolution of traditional corporate network perimeters and distributed workforces. As a result, there’s growing interest in security strategies emphasizing security controls that span widely distributed assets — including multicloud ecosystems.

One such strategy that’s currently generating quite a bit of buzz is cybersecurity mesh architecture (CSMA).

The term “cybersecurity mesh” was coined by analyst firm Gartner, which called CSMA one of the top strategic technology trends of 2022. Gartner defines cybersecurity mesh architecture as a “common, broad and unified approach … [that] extend[s] security beyond enterprise perimeters.” In Gartner’s view, CSMA focuses on composability, scalability, and interoperability to create a collaborative ecosystem of security tools. Somewhat optimistically, Gartner predicts that “organizations adopting a cybersecurity mesh architecture to integrate security tools to work as a cooperative ecosystem will reduce the financial impact of individual security incidents by an average of 90% by 2024.”

Like zero trust, the cybersecurity mesh model is well suited for today’s cloud applications and workloads since it re-envisions the perimeter at the identity layer and centers upon unifying disparate security tools into a holistic, interoperable ecosystem.

The emphasis on composability, scalability, and interoperability means that CSMA can move security teams from managing fragmented, individually configured services to deploying best-of-breed solutions that work together to mature the organization’s security posture. To achieve this end, though, multiple vendors will need to adopt open, standards-based approaches to interoperability.

As the concept of CSMA becomes more and more popular, however, questions remain. Will organizations invest in zero trust and CSMA side by side as they advance along the path to modernization? Both approaches are, after all, complementary, and building a resilient CSMA will enable an organization to achieve zero trust objectives. And do enough best-of-breed solutions exist that can integrate successfully to deliver the outcomes enterprises want from CSMA in the real world?

The idea of the cybersecurity mesh relies on assumptions about how widely available truly composable security services really are. These solutions feature an architecture designed to scale in a more agile fashion through an API-first approach — enabling flexibility and multicloud ecosystem management. CSMA also calls for common frameworks for everything from analytics to threat intelligence and security controls that can communicate via APIs.

An effective mesh architecture will also demand stronger, centralized policy management and governance. It’ll be essential to orchestrate better least-privilege access policies, which organizations can achieve by using a centralized policy management engine in conjunction with distributed enforcement. Security leaders must apply artificial intelligence/machine learning-based policies at the identity layer and extend these policies across the entirety of the access path — from device or endpoint to workload or application — to create integrated security out of an array of individual components.

Although CSMA remains more of a concept than an architecture at this point, there are three ways that security leaders can begin thinking about how to start deriving value.

Look to Deploy Composable Cybersecurity Technologies
On average, every large organization runs 47 different cybersecurity toolswithin its environment, leaving security teams to spend unsustainable amounts of time and effort managing complex, unwieldy integrations. By taking an API-first and standards-based approach, organizations can make everything a service. This way, security tools can talk to one another, sharing context and risk intelligence.

While open standards have seen increased adoption in many other areas of IT, the cybersecurity industry has lagged behind. Stakeholders across the industry need to work together to ensure that risk, identity context, usage, and other telemetries are effortlessly consumable across different solutions. This way, for instance, the secure email gateway can “talk” to the network firewall, and both can inform authentication decisions.

Centralize Policy Management Across All Your Security Tools
This isn’t simple. It will take a concerted effort to consolidate all security policies, including identity and access policies, in your environment and additional work to streamline this across multiple security tools. You’ll need to incorporate a central policy engine that can decide whether to grant, deny, or revoke access to resources for entities across the organization. And you’ll need to ensure that your organization administers and enforces these policies across every device and resource in the environment, no matter how widely distributed they may be.

Establish KPIs and Track Them
This is the only way to ensure that your CSMA genuinely works well together and delivers the intended results. Your organization should identify which metrics are essential to track and report, while keeping in mind that there may be multiple levels of KPIs to address. For example, a CISO may wish to report specific KPIs at the board level to show the CSMA strategy is impacting business outcomes — while individual teams will need to measure separate KPIs to assess security posture and overall cyber resiliency. 

Current trends like the large-scale adoption of remote work and increasing reliance on hybrid and multicloud infrastructures won’t reverse themselves anytime soon. To meet the modern enterprise’s ever-growing requirements for agility, security leaders must carefully examine their existing security infrastructure to find opportunities to bring previously siloed solutions together. Whether this will become known as CSMA or simply “enhanced interoperability and efficiency” in the months and years to come remains to be seen, but the need is pressing.

Article link: https://www.darkreading.com/operations/building-a-cybersecurity-mesh-architecture-in-the-real-world

Every Child Counts!

Posted by timmreardon on 04/13/2022
Posted in: Uncategorized. Leave a comment

Lorraine and Joyce, of Every Child Counts, Inc., delivered 152.3 lbs. of non-perishable food items to Janet, our Food Services Community Engagement Manager. The generous donation is in keeping with the organization’s mission, “To improve the lives of children from birth to 18 years old.” #everychildcounts #fooddonations #foodinsecurity #chestereastside

To Aid Digital Transformation, Army Eyes ‘One Cloud’ And Faster Acquisition – Breaking Defense

Posted by timmreardon on 04/12/2022
Posted in: Uncategorized. Leave a comment

By Theresa Hitchens on October 13, 2021 at 3:17 PM

AUSA: The Army is looking to create a unified cloud environment as a key piece of its new Army Digital Transformation Strategy (ADTS) aimed at centralizing its vast numbers of computer systems, data standards, cloud capabilities and cybersecurity procedures. And to that end, the service also is seeking to expand its use of non-traditional acquisition authorities, top officials explained today.

The strategy represents “a shift in terms of us starting to do things more at an enterprise, centralized level,” Raj Iyer, the Army’s chief information officer (CIO), told reporters in the margin of the annual Association of the United States Army (AUSA) trade show. “The Army in the past has always executed traditional IT in a very decentralized way — we let every command do their own thing. And that’s all led to a lot of silos of excellence over the years. Now, if you look at the requirements for multi-domain operations, that model doesn’t work anymore.”

RELATED: ‘Global By Nature’: Generals Say Unified Network Is ‘Operational Imperative’

The CIO office’s press to unify its “enterprise and tactical clouds” — and accelerate migration of data to that new cloud architecture in a standardized way — thus is a major focus of the ADTS.

“For cloud migration, it’s key that the office of CIO establishes the standards to do that migration,” stressed Brig. Gen. Matt Easley during the press roundtable. “We can’t allow every program office to go out and move to a cloud environment of their own their own design. We have to tell them the data standards we want them to use, the architecture standards, the cybersecurity standards on how we want them connected, and how to fuse that data to make that data usable and visible to the rest of the force.”

The service sees its multi-pronged $15 billion digital modernization effort as a top priority, the officials said, because it underpins the Army’s ability to plug and play into DoD’s Joint All Domain Command and Control (JADC2) strategy. Markowitz said the service has been working closely with the Joint Staff’s J6 directorate for Command, Control, Communications, & Computers/Cyber, Lt. Gen. Dennis Crall. In particular, this involves using contingency operations, such as the Afghanistan evacuation, and exercises, including Project Convergence, designed to figure out how to share Army information and data with the Combatant Commands, he said.

RELATED: DISA Head: DoD Working To Modernize ICAM, C2, Data Use

“We’re trying to experiment in real time with ongoing operations or exercises, kind of building a data foundation for a Combatant Command level, and for the Army’s interest we really want to make sure that data structure of how information flows is common across all Combatant Commands,” he said.

Mixing ‘Colors Of Money’

Iyer said that the ADTS also represents a shift in how the service works to encourage innovation and bring in industry partners, he said, including changing its acquisition approach.

While the Army, like all the services, faces challenges due to resource constraints, with his $15 billion annual budget, Iyer said, “money is not the problem” in implementing the digital transformation. It does mean having to divest its multiple individual data centers to invest instead in creating “one cloud.” A bigger issue is figuring out how to reform how the Army approaches budgeting.

Iyer said he has been talking with congressional staffers about how the Army can have more flexibility in the Planning, Programming, Budgeting and Execution (PPBE) process, and in how it funds digitization and cybersecurity  across “colors of money” — that is, separate budget pots for research and development, procurement and operations and maintenance.

“We are absolutely in favor of some reform, especially when it comes to how we budget for digital, and then cyber quite frankly, because our cyber threats are changing and evolving all the time. The way the PPBE process works is that you plan for something five years in advance, and then you program for it, and then you wait and five years later you get the money to execute. But we know how fast technology changes, we know how fast the the threats in the cyberspace are changing. And so, it’s a question about the flexibility the process to be able to do things.”

And while Congress has given the Defense Department more ability to use non-traditional acquisition tools, such as Broad Agency Announcements and Other Transaction Authorities,the Army up to now has been a bit cautious on how it applied them to software development, digitization and cybersecurity, David Markowitz, the service’s chief data officer, said during the roundtable.

“I’m not sure we’ve used the pilot authorities to the extent folks in Congress wanted us to. We’re a little slower than the Air Force, they’re a little more aggressive on these,” he said.

That’s in part because service leaders are still struggling a bit to understand exactly what is going on internally with investments.

“We have to do the internal work. Let’s be honest, we have difficulty seeing across the large scope of the Army how money is being spent in the digital area, and particularly on cyber security,” he added.

Article link: https://breakingdefense-com.cdn.ampproject.org/c/s/breakingdefense.com/2021/10/to-aid-digital-transformation-army-eyes-one-cloud-and-faster-acquisition/amp/

READ MORE AT BREAKING DEFENSE →

TOPICS

Army, Army Digital Transformation Strategy, AUSA 2021, cloud, cloud computing, cybersecurity, JADC2, Other Transaction Authority, Planning Programming Budgeting & Execution (PPBE), PPBE, Raj Iyer

QUANTUM INFORMATION SCIENCE – AFRL

Posted by timmreardon on 04/11/2022
Posted in: Uncategorized. Leave a comment

Quantum information science applies the best understanding of the sub-atomic world—quantum theory—to generate new knowledge and technologies. Quantum will revolutionize Air and Space Force operations.

The U.S. military is leading the acceleration of quantum research and development as first adopters for this fundamental technology to move the ball forward. Quantum will lead to technologies that will transform the war-fighting domain in revolutionary and unprecedented ways.

AFRL QUANTUM LABS

AFRL conducts and sponsors research across the globe, including in our laboratories in New York and New Mexico.

READ MORE ›

ULTRACOLD ATOMS

AFRL’s Quantum Sensing & Timing (QST) group seeks to take advantage of Nobel-Prize winning cold-atoms physics and related techniques to develop solutions for critical DoD problems in positioning, navigation and timing.

READ MORE ›

PHOTONIC MICROCOMBS

Photonic integrated circuits (PICs) will play a key role in transitioning quantum-enabled technologies beyond the laboratory. Our team investigates novel photonic components including microcombs and PIC-compatible laser sources.

READ MORE ›

LEVITATED OPTOMECHANICS

AFRL’s Quantum Sensing & Timing (QST) group seeks to use optically-levitated nanoparticles to develop solutions for critical problems in navigation and communication. The focus is on employing cutting-edge physics to develop sensors that are functional in a wide variety of situations.

READ MORE ›

ATOMIC CLOCKS & TIMING

AFRL’s Quantum Sensing & Timing (QST) group looks into the development of advanced atomic clocks to further improve time measurements and investigates ways to use and distribute the precise time.

READ MORE ›

TRAPPED IONS

AFRL’s trapped ion team investigates quantum mechanics and quantum information science with the long-term goal of constructing a quantum network made for processing and transmitting quantum information.

READ MORE ›

QUANTUM ALGORITHMS

The AFRL Quantum Algorithms group explores the design and application of quantum algorithms across research topics such as quantum optimization, algorithms, and quantum machine learning. The team also utilizes noisy, intermediate-scale quantum (NISQ) devices.

READ MORE ›

INTEGRATED PHOTONICS AND PHOTON QUBITS

The mission of the AFRL’s Quantum Information Processing Group is to generate, manipulate/process, distribute and analyze quantum entanglement both locally and distributed over processing nodes in a quantum network consisting of photon-based and memory-based quantum bits.

READ MORE ›

SUPERCONDUCTING & HYBRID QUANTUM SYSTEMS

The superconducting and hybrid quantum systems team at Rome Labs seeks to develop novel superconducting architectures and cross-modality quantum interface hardware as building blocks for use in quantum networking nodes.

READ MORE ›

STRATEGIC ATOMIC NAVIGATION DEVICES AND SYSTEMS (SANDS)

Archive Content | The SANDS program invested in Quantum Timing and Sensing components to improve the DoD’s Position, Navigation and Timing (PNT) warfighting capability.

READ MORE ›

Article link: https://afresearchlab.com/technology/quantum/

Why People Get Away with Being Rude at Work – HBR

Posted by timmreardon on 04/11/2022
Posted in: Uncategorized. Leave a comment

by 

  • Shannon G. Taylor,
  • Donald H. Kluemper,
  • W. Matthew Bowler,
  • Jonathon R. B. Halbesleben

July 10, 2019

Summary.   People who experience workplace rudeness report lower engagement, suffer more mental and physical health problems, and are more likely to burn out and quit their jobs. But while some research has indicated leaders take reports of bad behavior seriously, get the facts, and punish offenders, a new series of studies paints a much bleaker picture. First, researchers show that victims of rudeness were largely perceived by their manager as perpetrators of rude behavior. And the employees who were reported as being rude to others weren’t seen that way by their manager under two conditions: when they had a tight relationship with the boss or were high performers. Second, victims of rudeness were perceived as performing considerably worse by research participants than employees who hadn’t been mistreated, regardless of the employees’ actual performance. To address this, leaders must become more aware of their biases and how to prevent them from affecting their decision making.close

Bad behavior at work can have very real consequences. People who experience workplace rudeness, for example, report lower engagement, suffer more mental and physical healthproblems, and are more likely to burn out and quit their jobs. And nearly all of us are affected by rudeness and other types of workplace misbehavior, like interrupting and exclusion: Estimates suggest 98% of employees are on the receiving end over the course of a year.

Given bad behavior’s prevalence and impact, surely leaders take reports of it seriously, get the facts, and punish offenders, right? Some scholars have noted that, when information about misbehavior surfaces, savvy leaders know better than to blame the messenger. Unfortunately, our research paints a picture that is much bleaker.

We set out to investigate how people in positions of power view victims and perpetrators of workplace misbehavior. We first studied an organization that operates a chain of casual dining restaurants. We gave each employee a list of the names of every other employee who worked in their restaurant, and asked them to report who they were rude to and who was rude to them. We then asked managers to evaluate the behavior of each employee. Across the five restaurants we studied, 149 of the 169 employees (88%) and 13 of the 14 managers (93%) participated. Notably, those employees who reported being victims of rudeness were largely perceived by their managers as perpetrators of rude behavior. And the employees who were reported as being rude to others weren’t seen that way by their managers under two conditions: they had a tight relationship with the boss or were high performers.

To determine whether our findings applied outside of this organization, we enlisted the help of our undergraduate students. We asked them to recruit working adults from among their friends and family so that we could survey employees and managers from a wide variety of industries, organizations, and jobs. Employees reported in an online survey how frequently they experienced and engaged in rude behavior at work, and they provided the name and email address of their manager, who then rated the employee’s behavior in a separate online survey. We anonymized and tracked 372 leader-follower pairs from an assortment of professions, including office workers, mechanics, dental hygienists, plumbers, nurses, and many others. Sure enough, we found the same results. It seems leaders in all sorts of work settings fall prey to this bias when evaluating their employees’ behavior.

These two studies were telling, but they had an important limitation: Because employees who experience rudeness may also be rude themselves, as our earlier research has shown, bosses who blame victims might actually be evaluating these employees accurately. That is, these victims might also be perpetrators. If so, leaders’ evaluations might not be biased after all.

To rule out this possibility, we conducted two experiments to separate employees’ experiences of rudeness from their acts of rudeness. We recruited working professionals from our MBA courses and from online forums like LinkedIn. We instructed participants to imagine that they had been promoted into a management position and had been asked by their supervisor to assess their subordinates after observing them on the job over the past few weeks. We then presented participants with 10 fictitious employee profiles and asked them to conduct their assessments carefully. Some of the employees to be rated had experienced rudeness and had also behaved rudely. One such profile looked like this:

Chris has been with the organization almost 2 years and has a little more than 5 years of work experience. Chris appears to be a poor performer: sometimes late to work, doesn’t always work hard, not very knowledgeable on the job. Chris uses sarcasm that offends others, stares at others disapprovingly, and is cranky and short with coworkers. Coworkers sometimes avoid consulting with Chris when they would normally be expected to, make offensive jokes about Chris, and treat Chris as unimportant.

Other employees had been mistreated but had never mistreated others, like this one:

Alex has been with the company for about 2 years and has 6 years of work experience. Alex appears to be a very good performer at work: never tardy, puts forth a lot of effort, knowledgeable of core job tasks. You have not observed Alex making inappropriate comments toward coworkers, and Alex seems to be polite and courteous toward others when you’re around. However, coworkers sometimes intentionally “speak over” Alex, one was found reading Alex’s personal email, and others often roll their eyes at Alex.

We also included some profiles where the employee hadn’t been mistreated:

Taylor has 6 years of work experience and joined the company about 2 years ago. Taylor seems like an exceptional performer: arrives on schedule, works diligently, knowledgeable on the job. Taylor appears to address others in a professional manner at all times and does not give others hostile looks, stares, or sneers. Coworkers appear to be polite toward Taylor and treat Taylor with dignity and respect.

When we crunched the numbers, we found that participants perceived victims as having engaged in misbehavior. And by presenting participants with clear information that some employees did not behave rudely (like Alex), we were able to demonstrate that victims are blamed for their mistreatment even when they’ve done nothing wrong.

It gets worse: We also wanted to see if leaders’ bias toward victims extended to their assessments of the victims’ job performance, even when we provided concrete information about whether the employee was a high performer (like Alex) or a low performer (like Chris). It does: Victims of rudeness were perceived as performing considerably worse on the job than employees who hadn’t been mistreated, regardless of the employees’ actual performance. As performance ratings often have a substantial impact on compensation and promotion decisions, our results show that victims of workplace mistreatment can be adversely impacted in several other important ways, adding insult to injury.

So, how can leaders combat bias when evaluating employees? We recommend leaders receive training similar to that undergone by judges and arbitrators, who are taught to distinguish between relevant and irrelevant information. Homing in on job-relevant behaviors, whether during interviews or performance appraisals, can effectively reduce subjectivity and enhance decision accuracy. But because unrelated contextual and personal factors can influence the outcome — even among highly skilled judicial decision makers — training should also increase leaders’ awareness of the forces that may be influencing their decisions. Organizations might take a page from the Federal Judicial Center, which runs a program — as part of what is affectionately referred to as “baby judge school” — that does just that: It trains new judicial appointees to become more aware of their biases and prevent those biases from affecting their decision making.

Given the central role leaders play as decision makers in the workplace, it’s critical that they assess employee behavior fairly and accurately. To our dismay, our study discovered a tendency on the part of managers to blame employees for the mistreatment they experience. For those leaders responsible for evaluating others at work, we hope our research reminds you to be more judicious.

Article link: https://hbr.org/2019/07/why-people-get-away-with-being-rude-at-work?

  • Shannon G. Taylor is an associate professor of management at the University of Central Florida. His research focuses on leadership and workplace mistreatment.
  • DKDonald H. Kluemper is an associate professor in the department of managerial studies and co-director of the Institute for Leadership Excellence and Development at the University of Illinois at Chicago. He conducts research on personality, leadership, and workplace mistreatment.
  • WBW. Matthew Bowler is an associate professor in the Spears School of Business at Oklahoma State University. His research interests include leadership, social networks, and employee performance.
  • JHJonathon R. B. Halbesleben is the HealthSouth Chair of Health Care Management and Senior Associate Dean of the Culverhouse College of Commerce at the University of Alabama. His research focuses on employee stress and health

Posts navigation

← Older Entries
Newer Entries →
  • Search site

  • Follow healthcarereimagined on WordPress.com
  • Recent Posts

    • By Barring Profits on Basic Coverage, Switzerland Keeps Insurers from Denying Care – Commonwealth Fund 10/19/2026
    • Patients’ Perspectives on AI in Primary Care – Commonwealth Fund 09/11/2026
    • Bitcoin Mining Energy Footprint 08/06/2026
    • Closing the AI Hype Gap 08/05/2026
    • Why Artificial Intelligence is Neither Artificial, Nor Intelligent 07/31/2026
    • Agentic AI, explained 07/05/2026
    • Heeding the pope’s call to ensure AI protects human dignity – MIT Sloan Management 06/01/2026
    • Association between Wealth and Mortality in the United States and Europe – New England Journal of Medicine 05/30/2026
    • U.S. Health Care from a Global Perspective, 2026 – The Commonwealth Fund 05/30/2026
    • Anthropic co-founder Chris Olah’s remarks on Pope Leo XIV’s encyclical “Magnifica humanitas” 05/28/2026
  • Categories

    • Accountable Care Organizations
    • ACOs
    • AHRQ
    • American Board of Internal Medicine
    • Big Data
    • Blue Button
    • Board Certification
    • Cancer Treatment
    • Data Science
    • Digital Services Playbook
    • DoD
    • EHR Interoperability
    • EHR Usability
    • Emergency Medicine
    • FDA
    • FDASIA
    • GAO Reports
    • Genetic Data
    • Genetic Research
    • Genomic Data
    • Global Standards
    • Health Care Costs
    • Health Care Economics
    • Health IT adoption
    • Health Outcomes
    • Healthcare Delivery
    • Healthcare Informatics
    • Healthcare Outcomes
    • Healthcare Security
    • Helathcare Delivery
    • HHS
    • HIPAA
    • ICD-10
    • Innovation
    • Integrated Electronic Health Records
    • IT Acquisition
    • JASONS
    • Lab Report Access
    • Military Health System Reform
    • Mobile Health
    • Mobile Healthcare
    • National Health IT System
    • NSF
    • ONC Reports to Congress
    • Oncology
    • Open Data
    • Patient Centered Medical Home
    • Patient Portals
    • PCMH
    • Precision Medicine
    • Primary Care
    • Public Health
    • Quadruple Aim
    • Quality Measures
    • Rehab Medicine
    • TechFAR Handbook
    • Triple Aim
    • U.S. Air Force Medicine
    • U.S. Army
    • U.S. Army Medicine
    • U.S. Navy Medicine
    • U.S. Surgeon General
    • Uncategorized
    • Value-based Care
    • Veterans Affairs
    • Warrior Transistion Units
    • XPRIZE
  • Archives

    • October 2026 (1)
    • September 2026 (1)
    • August 2026 (2)
    • July 2026 (2)
    • June 2026 (1)
    • May 2026 (12)
    • April 2026 (4)
    • March 2026 (9)
    • February 2026 (6)
    • January 2026 (8)
    • December 2025 (11)
    • November 2025 (9)
    • October 2025 (10)
    • September 2025 (4)
    • August 2025 (7)
    • July 2025 (2)
    • June 2025 (9)
    • May 2025 (4)
    • April 2025 (11)
    • March 2025 (11)
    • February 2025 (10)
    • January 2025 (12)
    • December 2024 (12)
    • November 2024 (7)
    • October 2024 (5)
    • September 2024 (9)
    • August 2024 (10)
    • July 2024 (13)
    • June 2024 (18)
    • May 2024 (10)
    • April 2024 (19)
    • March 2024 (35)
    • February 2024 (23)
    • January 2024 (16)
    • December 2023 (22)
    • November 2023 (38)
    • October 2023 (24)
    • September 2023 (24)
    • August 2023 (34)
    • July 2023 (33)
    • June 2023 (30)
    • May 2023 (35)
    • April 2023 (30)
    • March 2023 (30)
    • February 2023 (15)
    • January 2023 (17)
    • December 2022 (10)
    • November 2022 (7)
    • October 2022 (22)
    • September 2022 (16)
    • August 2022 (33)
    • July 2022 (28)
    • June 2022 (42)
    • May 2022 (53)
    • April 2022 (35)
    • March 2022 (37)
    • February 2022 (21)
    • January 2022 (28)
    • December 2021 (23)
    • November 2021 (12)
    • October 2021 (10)
    • September 2021 (4)
    • August 2021 (4)
    • July 2021 (4)
    • May 2021 (3)
    • April 2021 (1)
    • March 2021 (2)
    • February 2021 (1)
    • January 2021 (4)
    • December 2020 (7)
    • November 2020 (2)
    • October 2020 (4)
    • September 2020 (7)
    • August 2020 (11)
    • July 2020 (3)
    • June 2020 (5)
    • April 2020 (3)
    • March 2020 (1)
    • February 2020 (1)
    • January 2020 (2)
    • December 2019 (2)
    • November 2019 (1)
    • September 2019 (4)
    • August 2019 (3)
    • July 2019 (5)
    • June 2019 (10)
    • May 2019 (8)
    • April 2019 (6)
    • March 2019 (7)
    • February 2019 (17)
    • January 2019 (14)
    • December 2018 (10)
    • November 2018 (20)
    • October 2018 (14)
    • September 2018 (27)
    • August 2018 (19)
    • July 2018 (16)
    • June 2018 (18)
    • May 2018 (28)
    • April 2018 (3)
    • March 2018 (11)
    • February 2018 (5)
    • January 2018 (10)
    • December 2017 (20)
    • November 2017 (30)
    • October 2017 (33)
    • September 2017 (11)
    • August 2017 (13)
    • July 2017 (9)
    • June 2017 (8)
    • May 2017 (9)
    • April 2017 (4)
    • March 2017 (12)
    • December 2016 (3)
    • September 2016 (4)
    • August 2016 (1)
    • July 2016 (7)
    • June 2016 (7)
    • April 2016 (4)
    • March 2016 (7)
    • February 2016 (1)
    • January 2016 (3)
    • November 2015 (3)
    • October 2015 (2)
    • September 2015 (9)
    • August 2015 (6)
    • June 2015 (5)
    • May 2015 (6)
    • April 2015 (3)
    • March 2015 (16)
    • February 2015 (10)
    • January 2015 (16)
    • December 2014 (9)
    • November 2014 (7)
    • October 2014 (21)
    • September 2014 (8)
    • August 2014 (9)
    • July 2014 (7)
    • June 2014 (5)
    • May 2014 (8)
    • April 2014 (19)
    • March 2014 (8)
    • February 2014 (9)
    • January 2014 (31)
    • December 2013 (23)
    • November 2013 (48)
    • October 2013 (25)
  • Tags

    Business Defense Department Department of Veterans Affairs EHealth EHR Electronic health record Food and Drug Administration Health Health informatics Health Information Exchange Health information technology Health system HIE Hospital IBM Mayo Clinic Medicare Medicine Military Health System Patient Patient portal Patient Protection and Affordable Care Act United States United States Department of Defense United States Department of Veterans Affairs
  • Upcoming Events

Blog at WordPress.com.
healthcarereimagined
Blog at WordPress.com.
  • Subscribe Subscribed
    healthcarereimagined
    Join 149 other subscribers

    Have a WordPress.com account? Log in now.

  • healthcarereimagined
    View site in Reader
    Manage subscriptionsSign upLog in
    Report this content
    Collapse this bar
Loading Comments...