February 1,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Data Model Discussion IHE Face 2 Face February 1, 2010 Profile.

Slides:



Advertisements
Similar presentations
January 19,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Standards and Transaction Discussion IHE TCON -2 January.
Advertisements

Healthcare Provider Directory (HPD) Data Schema Discussion
© 2011, Data Interchange Standards Association Provider Directory Presentation to: HIT Standard Committee Privacy & Security Work Group Presented by: Don.
Legal Work Group Developing a Uniform EHR/HIE Patient Consent Form.
Directory and Trust Services (D&TS) Define an Abstract Model Purpose: Document a common terminology that the group can use between the various tracks Identify.
How To Get To The Winners Circle with Your Patient Portal; Our Challenges To Get To The Finish Line. Julie Patterson, Baptist Health Carey Ronan, MHA,
NHS eProcurement Strategy Trade Association Meeting 24 th November 2014DH – Leading the nation’s health and care.
CREDENTIALING Where does the Board fit in? Robert P. Redwine President, Board of Directors Blount Memorial Hospital Maryville, Tennessee.
Proposed Technical Architecture for California HIE Services Walter Sujansky Sujansky & Associates, LLC Presentation to NHIN-Direct Security and Trust Work.
Health Care Careers Education Aspects. Copyright © 2004 by Thomson Delmar Learning. ALL RIGHTS RESERVED.2 Accrediting Agencies Purpose: to establish standards.
HIPAA – Privacy Rule and Research USCRF Research Educational Series March 19, 2003.
Increasing public concern about loss of privacy Broad availability of information stored and exchanged in electronic format Concerns about genetic information.
TM The HIPAA Privacy Rule: Safeguarding Health Information in Research and Public Health Practice Centers for Disease Control and Prevention Beverly A.
S&I Framework Provider Directories Initiative esMD Work Group October 19, 2011.
FERPA: Family Educational Rights and Privacy Act.
Project Update : Claims/Clinical Linkage Project MHDO Board of Directors June 6, 2013.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
August 12, Meaningful Use *** UDOH Informatics Brown Bag Robert T Rolfs, MD, MPH.
EMS Systems & The Roles of The Advanced EMS Professional Past, Present & Future.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin – Medicity/THSA.
PELICAN Keys to Quality – GSD Session 11 August 26th, 2008.
January 5, 2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Data Model Discussion IHE Tcon January 5, 2010.
January 19,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Standards and Transaction Discussion IHE Face 2 Face February.
SMART Agency Tipsheet Staff List This document focuses on setting up and maintaining program staff. Total Pages: 14 Staff Profile Staff Address Staff Assignment.
IHE Radiology –2007What IHE Delivers 1 Christoph Dickmann IHE Technical Committee March 2007 Cross Domain Review PCC.
Sanzi-1 CSE5 810 CSE5810: Intro to Biomedical Informatics Dynamically Generated Adaptive Credentials for Health Information Exchange Eugene Sanzi.
Example of Medical Record Elements
SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 1 February 3, 2010 List of HPD Use Cases:  Yellow Pages/Contact Data Query  Look up providers and their associations.
Hospital maintain various indexes and register so that each health records and other health information can be located and classified for Patient care.
Patient Care Coordination Tone Southerland Greenway Medical Technologies Co-chair, IHE PCC Marcia Veenstra Senior Health Inc. Co-chair, IHE PCC Nursing.
Interoperability and Health Information Exchange Workgroup April 2, 2015 Micky Tripathi, chair Chris Lehmann, co-chair 1.
TATS – View/Update Consultant Profile Department of Health and Human Services Health Resources and Services Administration HIV/AIDS Bureau.
OpenPASS Open Privacy, Access and Security Services “Quis custodiet ipsos custodes?”
FERPA: What you Need to Know The Family Educational Rights and Privacy Act & SEI.
Component 11/Unit 8b Data Dictionary Understanding and Development.
HIT Policy Committee NHIN Workgroup Recommendations Phase 2 David Lansky, Chair Pacific Business Group on Health Danny Weitzner, Co-Chair Department of.
© 2009 The McGraw-Hill Companies, Inc. All rights reserved. 1 McGraw-Hill Chapter 2 The HIPAA Privacy Standards HIPAA for Allied Health Careers.
Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.
January 7,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Data Model Discussion IHE TCON January 7, 2010.
X12 - February 4, National Provider Identifier A new identifier: The NPI is the standard unique health identifier for health care providers. Prepared.
School of Health Sciences Week 4! AHIMA Practice Brief Fundamentals of Health Information HI 140 Instructor: Alisa Hayes, MSA, RHIA, CCRC.
November 10, 2009 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Health IT Provider Registry IHE Proposal Overview Proposed Editor: Shanks Kande, Nitin Jain.
Chapter 7: Indexes, Registers, and Health Data Collection
October 7, 2009 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Health IT Provider Registry IHE Proposal Overview Proposed Editor: Shanks Kande, Marty Prahl.
Draft Provider Directory Recommendations Begin Deliberations re Query for Patient Record NwHIN Power Team July 10, 2014.
Costa Rica´s business registry: Directory of institutional units and establishments Contacts: Odilia Bravo:
HIT Policy Committee NHIN Workgroup HIE Trust Framework: HIE Trust Framework: Essential Components for Trust April 21, 2010 David Lansky, Chair Farzad.
Electronic Submission of Medical Documentation (esMD)
Medical Eligibility Verifications 1. Medical Eligibility: Verifications Introduction After completing this course, you will be able to: Recognize shared.
HITPC Meaningful Use Stage 3 RFC Comments July 22, 2013 Information Exchange Workgroup Micky Tripathi.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
Provider Directories Tasking, Review and Mod Spec Presentation NwHIN Power Team April 17, 2014.
Nursing My specific job My specific job is a RN coordinator.
Introduction to Health Careers Over 200 different careers in healthcare Education requirements vary and depend on many factors Preparation begins in high.
APRN Faculty Toolkit: ANCC Certification Overview © 2010 American Nurses Credentialing Center.
*Facility ID # : _____________ *HCW ID # : _____________ Social Security # : ___ ___ ___ - ___ ___ - ___ ___ ___ ___ Secondary ID # : _____________ HCW.
What IHE Delivers Healthcare Provider Directories IHE IT Infrastructure Planning Committee Eric Heflin - Medicity.
Training and Education Suffix Abbreviation Text Final Recommendations VCDE Small Group Lynne Wilkens, Linda Schmandt, Virginia Hetrick, Kristel Dobratz.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
© 2015 California Association of Health Information Exchanges Licensed under a Creative Commons Attribution Share-Alike 3.0 LicenseCreative Commons Attribution.
Trust Profiling for Adaptive Trust Negotiation
Introduction to Emergency Medical Care
Using the Oregon POLST Registry
Component 11 Configuring EHRs
The Oregon POLST Registry
Patient Medical Records
Using the Oregon POLST Registry
The Oregon POLST Registry
Presentation transcript:

February 1,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Healthcare Provider Directory (HPD) Data Model Discussion IHE Face 2 Face February 1, 2010 Profile Leads: Shanks Kande (SSA) Nitin Jain (IBM) Toby Briks-Fader (IBM)

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 2 February 1, 2010 Topics  HPD Overview  HPD Content Model Review  Next Steps

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 3 February 1, 2010 HPD Overview  This proposal recommends development of a unified approach for electronic lookup query where, upon initiated with a unique identifier or key demographic elements, an authorized user may obtain content of a unique provider entry with high reliability.  Beyond the query lookup functionality, there is a minimum set of transactions required to create and maintain the directory service, first of which is the ability to make additions and updates to provider entries.  The scope of this proposal focuses initially on the minimum “foundational” set required for defining a provider directory, resulting in a usable work product as well as recommendations for future phase expansions.

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 4 February 1, 2010 Use Cases Use CaseUse of HITPR Stakeholders Social Services Department Disability Determination  Identify claimant’s providers by demographics & affiliations  Locate providers’ electronic end points in the network to support directed electronic requests Claimants, Providers, SSA, Health Information Exchanges, Social Services programs Emergency Response  Contact providers and identify “Medical Reservists”  Verify provider credentials Citizens, Providers, Public health Officials, State & Local Epidemiologists, Response Workers Consumer Access to Provider List  Select provider of care list from registry to grant or deny access permissions  Alerts on provider demographic updates Consumers, Families, PHR vendors, providers E-Prescription  Prescriber credentials (DEA) validation  Identify & communicate with prescribers on drug recall Providers, Patients, Pharmaceuticals, Drug Safety Officials

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 5 February 1, 2010 HPD Content Model  The HPD Content Model supports the query for provider based on properties, relationships, and classifications Relationships Properties Classifications Provider

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 6 February 1, 2010 Metadata based Directory

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 7 February 1, 2010 Individual Provider View Individual Provider Alias Organization (s) Education (s) Department (s) Addresses (s) has is composed of (many) Is located at has business Relationship (s) Is composed of (many) Is housed in (many) Credential (s) Specialty has Has Provider has Business Relationship HIE/HIO belongs to with

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 8 February 1, 2010 Organization View Organization Specialty (s) Department (s) Facility (s)Addresses (s) is housed in (many) Is composed of (many) Which are at (Many) Business Relationship (s) Is Composed of (many) Is housed in (many) Credential (s) has Is located at Has AliasProvider has HIE/HIO belongs to Business Relationship has is housed in (many)

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 9 February 1, 2010 Use Case View Organization HIE/HIO Use Case Owner Owns May Support Business Use Case (s) May support Belongs to Owns AliasProvider Has

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 10 February 1, 2010 Attributes Provider Entity  HPD Provider ID – HPD Generated Identifier  Provider Status – active/inactive in HPD  Provider Validation Flag: determines if provider information has been validated for the HPD  Validation Source - Identifies the source that validated the information  Validation Date – the date this record is validated  Provider Type – Individual or Organization  Creation Date - the date a record in HPD record is effective from  Last Update Date - the date a record is last updated in the HPD Individual Provider  Provider First Name  Provider Middle Name  Provider Last Name  Provider Suffix  Provider Prefix  Language Spoken List  Provider Gender  Provider Race  Provider Birth Date  Provider Death Date  Provider Birth State Code  Provider Birth Country Code  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 11 February 1, 2010 Attributes Organization  Organization Name – name of a group or party other than an individual that render health care services  Organization Type  Organization Description  Last Update Date - the date a record is last updated in the HPD Provider Alias  Alias Last Or Organization Name - various names the provider is known by including maiden name or previous legal name  Alias First Name  Alias Middle Name  Alias Type Code - code identifying the type of alias name, e.g. professional name, doing business as (d/b/a) name, maiden name  Status: Active/Inactive  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 12 February 1, 2010 Attributes Address  HPD Location ID: HPD Generated Address ID  Location Purpose Type - type of address associated with the provider i.e. mailing, residence, practice etc  First Line Address  Second Line Address  City  Country Code  Zip Code  State Code  Location Description  Fax Number- Area Code + Number  Telephone Number - - Area Code + Number + Extension  Electronic URL List  Status: Active/Inactive  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 13 February 1, 2010 Attributes Specialty  Specialty Type: A major grouping of service(s) or occupation(s) of provider. E.g. Dermatology, Dental, Internal Medicine, Orthopedic, Pediatric etc.  Specialty Name: Provider’s specialization,, a specific medical service, a specialization in treating a specific disease. E.g. Bariatric Medicine, Geriatric Medicine, Pediatric Dermatology etc.  Specialty Role Type: Role of provider that further classifies the provider clinical responsibility. E.g. Physician, Licensed Practical Nurse, Midwife, Chiropractor, Nursing service  Status: Active/Inactive  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD Credential  Certification Type Name: Type of certification earned by a provider.  Certification Type Description  Certificate Verification Date  Certification License Number  Certificate Issuing Organization  Certificate State Code  Certificate Country Code: Country where certificate is valid  Certification Issue Date - date on which the certification was issued  Certification Renewal Date  Certification Status: Active/Inactive/Pending etc.  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 14 February 1, 2010 Attributes Provider Identifier  Identification Number – Unique Identifiers that may exist for a provider in a particular domain, state or country  Identifier Type: Type of identifier such as tax identification number, state issued number, National Provider Identifier, drug identifying number, social services number, etc.  Identifier Issuing Agency: Name of the agency that issues this identifier  Identifier Description  Deactivation Reason Text  State Code: State where this identifier is valid  Country Code: Country where this identifier is valid  Identifier Status - status of the identifier: active, inactive, revoked, dropped or suspended  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 15 February 1, 2010 Attributes Business Relationship This entity establishes relationship either between Individual & Organization, Organization & organization  HPD Business Relationship ID – HPD Generated Identifier for business relationship  Relationship From ID: HPD Provider Id from which business relationship originates  Relationship Target ID: HPD Provider Id to which business relationship is being established  Relationship Type - type which describes the business relationship between an Individual or Organization as defined in the HPD. (i.e. Individual provider "is member" of a health system)  Relationship Status – active/inactive/pending  Relationship Validation Flag - determines if relationship information has been validated  Relationship Number (local identifier) - unique number that an individual provider may be known by in a particular organization or department based on this business relationship. For example, an employee ID number in a hospital  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 16 February 1, 2010 Attributes HIE/HIO  HIE Name: Name of a Health Information Exchange/Network Organization.  HIE Contact Information - demographic information that allows contact with the designated individual who disseminates and receives information pertaining to an HIE/HIO (i.e. name or phone number).  HIE Identifier (OID): Unique Identifier assigned to this HIE.  HIE Certification Status: Active/Inactive/Pending status of HIE Certification by a Certifying body  HIE Certification Agency: Certification body certifying a HIE  Data Sharing Agreement Level - level of the Data Sharing Agreements for the HIE/HIO such test/production  HIE Network URL List: Service end points of the HIE network.  HIE Status: Active/Inactive  Creation Date - the date a record in HPD record is created  Last Update Date - the date a record is last updated in the HPD

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 17 February 1, 2010 Attributes Business Use Case  Use Case Name – name of the the Business Services (Use Cases) in which a HIE participates  Use Case Service Description  Use Case Service Status  Effective End Date  Effective Start Date Use Case Owner  Use Case Owner Address  Use Case Owner Phone Number  Use Case Owner Contact Name  Use Case Owner Name - the entity (Agency, individual) who develops and owns use cases that describe business service

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 18 February 1, 2010 Next Steps  Discussion on Data Modeling tool  Review Use Cases  Review Standards and Transaction

February 1,2010 SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT Backup Information

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 20 February 1, 2010 Use Case View

SOCIAL SECURITY ADMINISTRATION-HIT SUPPORT 21 February 1, 2010 Feedback and considerations on data model EntityAttribute/RelationshipChange Comments 1 DepartmentDelete 2 FacilityAdd a credentialing relationship with Individual Provider Add relationshipMay need a business relationship between Facility and Individual Provider 3 FacilityAdd a relationship to “Alias” 4 FacilityAdd a relationship to Business Relations Add relationshipBusiness relationship could exist between facility and provider (not department). 5 Education Delete 6 OrganizationAdd a relationship to Organization from Organization. Add relationshipNeeds a recursive relationship to document “an organization can be a supertype to zero, one or many subtype organizations. 7 Organization/ Individual Provider Add a privileges attributeAdd attributeA privilege distinguishes the type of “credentials” i.e. in good standing a individual provider has at a organization. 8 Individual /Education Add a credential attributeAdd attributeA “credentialing attribute will document educational degrees. 9 OrganizationAdd “governance”Add attributeGovernance should determine “privileges/credentialing of providers.