If you are a health organization you probably have or thinking of having a clinical data warehouse. A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more. Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit
More than 2 years have past since I wrote my article on the Fast Healthcare Interoperability Resources (FHIR®) standard and it’s time to do a quick status check and revisit the predictions I made back then. The FHIR standard continues the strong trajectory of adoption and is now used across the globe. The application programming interface (i.e. the FHIR API) is available in most major EHR systems today. According to the US Office of the National Coordinator Health Information Technology an estimated 85% of hospitals have FHIR in their systems. The NHS has been quick to adopt FHIR and the adoption curve in the UK is high. The NPfIT (NHS Care Record Service) HL7 V3 interfaces are being redeveloped in FHIR®, and new NHS specifications such as the CareConnect standard for secured Transfer of Care are being specified in FHIR® by default. Despite the industry enthusiasm about the potential of FHIR still the old and faithful HL7 v2 remains the predominant interoperability standard in use t