HSPC Profiles: Conformance and Interoperability. Definitions.

Slides:



Advertisements
Similar presentations
1 Authenticity Capture Prototype Matt Dunckley, STFC.
Advertisements

MHD-I: The Future Brad Genereaux February Agenda Review summary of original scope Review summary of high level feedback Highlight five different.
Health IT Workforce Curriculum Version 1.0 Fall Networking and Health Information Exchange Unit 4e Basic Health Data Standards Component 9/Unit.
HSPC Relationship to Other Initiatives
FHIR and HSPC Meeting July 7 Grahame Grieve.
CIMI Modelling Taskforce Workshop (Groningen) Dr Linda Bird 2 nd – 4 th December 2012.
QIDAM Issues and proposals for a logical model For discussion during HL7 WG Meeting in Jan 2014 Thursday Q3.
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
Catherine Hoang Ioana Singureanu Greg Staudenmaier Detailed Clinical Models for Medical Device Domain Analysis Model 1.
MOHH – Models Submission Dr Linda Bird 9 th August 2012.
Introduction to openEHR
SMART/FHIR Genomic Resources An overview... For latest see
Screening Maneuvers Improvement Facilitator Training Session 1 Day 1.
HL7 Standards Strategic and Tactical Use Charlie McCay
7M701 1 Software Engineering Software Requirements Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 5
José Costa Teixeira January 2015 Medication Data Capture and Management.
FEBRUARY 4, 2015 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE Modeling and Terminology.
Research-driven data standards CIMI 11 th April 2013.
A Use Case for SAML Extensibility Ashish Patel, France Telecom Paul Madsen, NTT.
AUGUST 21, 2014 STANLEY M. HUFF, MD CHIEF MEDICAL INFORMATICS OFFICER INTERMOUNTAIN HEALTHCARE HSPC Meeting Introduction.
Healthy Living Factors in Preventing Serious Disease ( Diabetes, Cancer Heart Attack, Stroke)
FHIM Overview How the FHIM can organize other information modeling efforts.
How do professional record standards support timely communication and information flows for all participants in health and social care? 1 Gurminder Khamba.
CIMI + FHIR Grahame Grieve 10-August 2015 Salt Lake City.
Profiling Metadata Specifications David Massart, EUN Budapest, Hungary – Nov. 2, 2009.
Standards Collaborative Membership Two-tiered model offers expanded benefits at no cost or reduced fees Registrants can choose their tier based on individual.
Standards Analysis Summary vMR – Pros Designed for computability Compact Wire Format Aligned with HeD Efforts – Cons Limited Vendor Adoption thus far Represents.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Conformance Mark Skall Lynne S. Rosenthal National Institute of Standards and Technology
Modeling Options HSPC Meeting June 17, 2015 Washington DC.
SMART/FHIR Genomic Resources
1 HITSP – enabling healthcare interoperability Current Framework and Fundamental Concepts  For those unfamiliar with the HITSP Harmonization Framework.
©2001 Sowerby Centre for Health Informatics at Newcastle Progress on Virtual Medical Record HL7 Salt Lake City.
CIDER - Today’s research, Tomorrow’s treatments Lab-2 September 15, 2010 Bijoy George, Program Manager, CBMI
Networking and Health Information Exchange Unit 5b Health Data Interchange Standards.
C++ Programming Basic Learning Prepared By The Smartpath Information systems
CIMI Survey results 1 Presented by Nicholas Oughtibridge.
Page 1 Model Development and Review CIMI/FHIR/HSPC Meeting August 11, 2015 Stan Huff Tom Oniki.
Logical Model Collaboration Scope, proposal, and next steps.
TEST, JAMES SEX: M AGE: 62 MRN: Vital Signs Heart Rate Blood Pressure Respiratory Rate Body Temperature Height Weight bpm systolic / diastolic.
Health Level 7- Templates SIG By Peter Elkin, Mayo Clinic Martin Kernberg, UCSF Angelo Rossi-Mori, Italy.
Ch- 8. Class Diagrams Class diagrams are the most common diagram found in modeling object- oriented systems. Class diagrams are important not only for.
® A Proposed UML Profile For EXPRESS David Price Seattle ISO STEP Meeting October 2004.
Algorithm Discovery and Design Objectives: Interpret pseudocode Write pseudocode, using the three types of operations: * sequential (steps in order written)
Leading Cause of Death Heart disease: 611,105 Cancer: 584,881 Chronic lower respiratory diseases: 149,205 Accidents (unintentional injuries): 130,557 Stroke.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Helping the Cause of Medical Device Interoperability Through Standards- based Test Tools DoC/NIST John J. Garguilo January 25,
Case Study: HL7 Conformance in VA Imaging Mike Henderson Principal Consultant Eastern Informatics, Inc.
7/2/2016 1:52 AM HL7 SOA-Aware Enterprise Architecture Executive Summary HITSP October 28, 2008 Executive Summary HITSP October 28, 2008.
Page  2 Accutane, a medication used to treat acne, has recently been linked to dangerous health conditions such as inflammatory bowel disease (IBD).
1.2 Reasoning Mathematically Two Types of Reasoning Remember to Silence Your Cell Phone and Put It in Your Bag!
HSPC Terminology and Information Model Initiative Susan Matney, PhD, RNC-OB, FAAN (Initiative Lead) Stan Huff, MD, FACMI, FHL7 11/6/2016.
11th HL7 Australia Conference, 13th December 2006
Figure 1: AFHIR Observation Resource Definition for systolic blood pressure with example in JSON. From: SMART on FHIR: a standards-based, interoperable.
Current Framework and Fundamental Concepts
TIM 58 Chapter 8: Class and Method Design
Intent (Thanks to Jim Fawcett for the slides)
A Brief Review of CIMI Progress, Plans, and Goals
clinFHIR Demonstration
Mapping IEEE PHD to FHIR - context
A holistic view on Vocabulary Binding
LHS – Care Team Value Sets
Mapping IEEE PHD to FHIR - context
_ Update Seth Blumenthal, MBA Director, Data & Innovation PCPI
Hypoglycemia: The Most Common Barrier to Effective Diabetes Management
CHEAR (Child Health Environmental Assessment Resource) Ontology
How to Use i2b2 URL to i2b2: Questions?
SNS College of Engineering Coimbatore
Presentation transcript:

HSPC Profiles: Conformance and Interoperability

Definitions

“Resource-level” Profiles: Profiles at the level at which FHIR defines resources (Patient, Observation, Procedure, Practitioner, Condition, etc.) “Detail-level” Profiles: Profiles at a more detailed level, e.g., profiles for Hematocrit, Glucose, Heart Rate, Body Weight, Diabetes, Pain, Ulcerative Colitis, Nausea, Rash, etc.

Definitions “Resource-level” Profiles: Profiles at the level at which FHIR defines resources (Patient, Observation, Procedure, Practitioner, Condition, etc.) “Detail-level” Profiles: Profiles at a more detailed level, e.g., profiles for Hematocrit, Glucose, Heart Rate, Body Weight, Diabetes, Pain, Ulcerative Colitis, Nausea, Rash, etc. HSPC intends to produce both levels of profiles.

Definitions (continued) “Narrow” a profile: Create a new profile that performs the following relative to an existing profile: Constrains value sets Constrains data type choices Specifies terminology bindings (where none was originally specified) Constrains cardinality Sets codes Declares “must support”

Definitions (continued) “Broaden” a profile: Create a new profile that performs the following relative to an existing profile: Adds extensions Expands value sets (where allowed)

Definitions (continued) “Broaden” a profile: Create a new profile that performs the following relative to an existing profile: Adds extensions Expands value sets (where allowed) Narrowing and Broadening may be done: Physically (new profile uses the original profile as the base) Logically (new profile is a sibling to the original profile and is only different from the original in “narrowing” ways)

Resource-Level Profiles

Notes of explanation

Resource-Level Profiles: DAF and HSPC Where necessary, HSPC will create derivatives of the DAF profiles with the intent of providing more generally-usable profiles to the community.

Resource-Level Profiles: Narrowing Where HSPC profiles “narrow” DAF profiles: Data that conform to the HSPC profiles will also conform to the DAF profiles. Not all DAF-conformant data will be HSPC-conformant.

Resource-Level Profiles: Broadening Where HSPC profiles “broaden” DAF profiles: Data that conform to the DAF profiles will also conform to the HSPC profiles. Not all HSPC-conformant data will be DAF-conformant.

Resource-Level Profiles: Broadening and Narrowing HSPC resource-level profiles will likely need to both narrow and broaden DAF profiles. Narrow: specify bindings constrain value sets and cardinalities Broaden: add extensions

Resource-Level Profiles: Broadening and Narrowing HSPC resource-level profiles will likely need to both narrow and broaden DAF profiles. Narrow: specify bindings constrain value sets and cardinalities Broaden: add extensions Consequently: Not all DAF-conformant data will be HSPC-conformant. Not all HSPC-conformant data will be DAF-conformant.

Resource-Level Profiles: Two Sets HSPC will support two sets of resource-level profiles: Set 1: The DAF profiles Set 2: The HSPC profiles that narrow and broaden DAF

Resource-Level Profiles: Two Sets HSPC will support two sets of resource-level profiles: Set 1: The DAF profiles Set 2: The HSPC profiles that narrow and broaden DAF Users of the two sets may not be interoperable. DAF profile instances won’t be conformant with HSPC profiles where HSPC profiles have made value set/code constraints. HSPC profile instances won’t be conformant with DAF profiles where HSPC profiles have added extensions.

Detail-Level Profiles

“True”Interoperability is delivered by detail-level HSPC profiles Specific Lab profiles Other observation profiles (heart rate, respiratory rate, pain, height, head circumference, etc.) Condition profiles (cancer, diabetes, Crohn’s disease, etc.) Procedure profiles (hysterectomy, colonoscopy, gastric bypass, etc.)

Detail-Level Profiles “True”Interoperability is delivered by detail-level HSPC profiles Specific Lab profiles Other observation profiles (heart rate, respiratory rate, pain, height, head circumference, etc.) Condition profiles (cancer, diabetes, Crohn’s disease, etc.) Procedure profiles (hysterectomy, colonoscopy, gastric bypass, etc.) Detail-level profiles constrain Resource-level profiles consequently, instances will not be conformant with Resource-level profiles.

Summary HSPC Members may use any one of three sets of profiles:

Summary HSPC Members may use any one of three sets of profiles: Detail-level profiles are necessary for true, plug- and-play interoperability.

Summary HSPC Members may use any one of three sets of profiles: Detail-level profiles are necessary for true, plug- and-play interoperability. NOT INTEROPERABLE

Risks Getting ONC-sponsored groups collaborating Carving the pertinent part out of their work and harmonizing (or not harmonizing) with it Mapping CIMI models and FHIR profiles Scalability of detail-level profile creation process Getting detail-level profiles reviewed A moving FHIR spec