Benjamin Flessner Email & Phone Number

As a software developer, Benjamin Flessner excels at making software work more efficiently and robustly, whatever the language. Complex problems are merely fun puzzles to be solved. At Epic, one of the largest medical records vendors in the US, he was instrumental in connecting healthcare systems across the country and even the globe, and ensured safe and meaningful exchange by developing tools and standards for interoperability. At Redox, Benjamin implemented a FHIR-based API and data warehouse from the ground up, augmenting a robust healthcare API with even richer clinical information. He also led work in pivoting from a proprietary data model to standard FHIR, including mapping HL7v2, C-CDA, and other standards to and from FHIR.As a co-chair of Health Level Seven's (HL7) Structured Document Working Group (SDWG), Benjamin actively supports authors and implementers of FHIR and Clinical Document Architecture (CDA) standards and regularly reviews newly published guides for technical problems to prevent implementation hurdles. Benjamin also regularly develops new examples and guidance in many areas of CDA implementation and has co-authored numerous guides including C-CDA, the C-CDA Companion Guide, and C-CDA on FHIR mapping and implementation.

Listed skills include Software Development, C#, Cda, Interoperability, and 20 others.

• 

  Member, Co-Chair Structured Documents Workgroup, C-Cda Examples Task Force Member

  Health Level Seven International

  2006 - Present

  Supports clinical standards development by ironing out difficulties in syntax and semantics. Co-editor of Consolidated Clinical Document Architecture (C-CDA), cited by 2015 government regulations for Meaningful Use. Ongoing contributor to new guides like the C-CDA Companion Guide - which provides up-to-date best practices for implementing C-CDA and meeting US Core Data for Interoperability (USCDI) data requirements - and the C-CDA on FHIR project which provides guidance on mapping the widely-used C-CDA format to new FHIR structures.Maintains technical artifacts like the base CDA schema, schematron validation tools, and core FHIR definitions. Educates the community in the use of these and other tools and helps Ongoing driver and supporter for future work in CDA and FHIR including development of user-friendly web-based standards, bidirectional mappings between FHIR and legacy standards, and tooling to make both development and implementation of these standards easier and faster for everyone.