web services

See the following -

Are Open Source Clinical Decision Support (CDS) Services Subject to HIPAA Regulations?

Clinical Decision Support (CDS) services such as HLN’s Immunization Calculation Engine (ICE) are modular, loosely-coupled components of larger systems accessed via web services in a service-oriented architecture (SOA). Under HIPAA, services provided to Covered Entities (CE) which involve protected health information (PHI) as defined in the statute are subject to the regulation. But are CDS services such as ICE subject to this regulation?

Read More »

Experts from BMW Group Research and Technology are developing in the research project webinos an open source platform for using mobile web applications across different devices.

Press Release | BMW Group, BMW Forschung und Technik GmbH | September 10, 2012

The infinite world of the web. Experts from BMW Group Research and Technology are developing in the research project webinos an open source platform for using mobile web applications across different devices. Read More »

Pharmaceutical and Biomedical Research using Agile Software

Andy Oram | EMR & EHR | January 18, 2016

Medical research should not be in a crisis. More people than ever before want its products, and have the money to pay for them. More people than ever want to work in the field as well, and they’re uncannily brilliant and creative. It should be a golden era. So the myriad of problems faced by this industry–sources of revenue slipping away from pharma companies, a shift of investment away from cutting-edge biomedical firms, prices of new drugs going through the roof–must lie with the development processes used in the industry...

Read More »

The Postmodern EHR: What are the Enablers?

Traditional monolithic EHR architectures focus on stability and standardization at the expense of agility. Along with innovation, cloud based deployment and integration of things, agility is the main differentiator when describing the requirements of application architecture for the Postmodern EHR. Achieving agility is impossible for the vast majority of healthcare applications today as they are an inseparable mix of code for user interface, decision logic, workflows and data definitions. New architectures promote agility and reuse by turning the applications inside out and layering the four types of programming into portals, rule engines, process engines and XML data. Let’s look at some examples, layer by layer:

The Postmodern EHR: The Data Layer

This second approach entails defining a data layer, which is the most important aspect of the Postmodern EHR architecture from my previous post. Why is this the most important layer? Most healthcare organizations are beginning to realize that their data is more valuable than their applications. Data has become a key asset, since good data is key to improving outcomes, managing chronic disease and enabling population health management. And it needs to be managed for the lifetime of the patient. Which application is going to last that long? What happens to health data when we switch applications?