HITSP General Lab Orders Open Survey Impart Lab Request Message Ability.


83 views
Uploaded on:
Category: People / Lifestyle
Description
The General Lab Orders work thing presents necessities for the sending and ... For instance, a lab may give back an alteration to a research center request saying that
Transcripts
Slide 1

HITSP General Lab Orders Public Review Communicate Lab Order Message Capability Provider Perspective TC | September 29, 2009 HITSP Capabilities Public Review Webinar

Slide 2

HITSP General Lab Orders Requirements and Design Public Comment Introduction & Review of Capabilities Schedule Technical Approach Public Comment HITSP Capabilities Public Review Webinar

Slide 3

HITSP General Lab Orders Requirements and Design Public Comment Introduction & Review of Capabilities Schedule Technical Approach Public Comment HITSP Capabilities Public Review Webinar

Slide 4

Introduction The reason for this Webinar is to share the new record made with a specific end goal to meet the General Lab Orders Extension/Gap and freely audit it preceding a one week remark period. This is only the prerequisites segment of the record, the full archives will be discharged for the conventional 4 week open remark period toward the beginning of November The General Lab Orders work thing presents necessities for the sending and accepting of an arrangement of research facility request, status and control messages. The Communicate Lab Order Message capacity was made keeping in mind the end goal to satisfy the necessities of the ONC General Lab Orders Extension/Gap HITSP Capabilities Public Review Webinar

Slide 5

Introduction – Co-Chairs and Staff HITSP Capabilities Public Review Webinar

Slide 6

Healthcare Information Technology Standards Program (HITSP) Providing particulars that coordinate different benchmarks to meet clinical and business requirements for sharing data: Develop determinations that address wide partner points of view Support testing and acceptance of details Catalyze endeavors of principles associations to acknowledge changes to address crevices and covers Enabling Interoperability between human services partners Specifying Standards expected to improve care quality and contain costs HITSP Capabilities Public Review Webinar

Slide 7

Constructs (single reason or reusable) Base or Composite Standards HITSP Interoperability Specifications Type 1: Base or Composite Standards A complete IS set gives a structure that characterizes A chain of importance of builds The part of every build The relationship of one build to another with regards to particular business and/or clinical prerequisites Interoperability Specification (build) Interoperability Specification (Complete Set) HITSP Capabilities Public Review Webinar

Slide 8

Capabilities and Service Collaborations Keys to Simpler Definition and Implementation of HITSP Specifications HITSP Capabilities Public Review Webinar

Slide 9

Service Collaboration (SC) Defines a models based secure framework required for interoperable data trades Includes a protected transport instrument with topology and different alternatives Uses HITSP Constructs to indicate the safe foundation Does not determine the substance of the data trade but rather may incorporate data to bolster the trade (e.g., approval data) HITSP Capabilities Public Review Webinar

Slide 10

Patient assent Management Delivery notice Email address/appropriation list Patient Identification Topology System-to-System Portable Media System-to HIE-to-HIE Service Collaboration Standards-based Secure Infrastructure Needed for Interoperable Information Exchanges HITSP Capabilities Public Review Webinar

Slide 11

Service Collaborations SC108 - Access Control SC109 - Security Audit SC110 - Patient Identification Management SC111 - Knowledge and Vocabulary SC112 - Healthcare Document Management SC113 - Query for Existing Data SC114 - Administrative Transport to Health Plan SC115 - HL7 Messaging SC116 - Emergency Message Distribution Element HITSP Capabilities Public Review Webinar

Slide 12

HITSP Capability Enables frameworks to address a business requirement for interoperable data trade Bridges between business, arrangement and execution sees: Defines an arrangement of data trades at a level pertinent to approach and business choices Supports partner necessities and business forms Defines data content and secure base Specifies utilization of HITSP develops adequately for usage Includes limitations and distinguishes particular system topologies HITSP Capabilities Public Review Webinar

Slide 13

What is a case of an ability? I need to trade a medicine with an Ambulatory of Long-Term Care (LTC) Organization System Roles Medication Order Prescriber Medication Order Filler Health Plan Health Information Exchange (HIE) Requirement: An association needs to trade a remedy with a walking association. The outline on the right shows how Capability 117 was collected to bolster this prerequisite. CAP117 – Communicate Ambulatory and Long Term Care Prescription HITSP Capabilities Public Review Webinar

Slide 14

Existing HITSP Capabilities – Clinical Operations HITSP Capabilities Public Review Webinar

Slide 15

Existing HITSP Capabilities – Public Health and Emergency Response; Administration and Finance HITSP Capabilities Public Review Webinar

Slide 16

Existing HITSP Capabilities - Security, Privacy, and Infrastructure HITSP Capabilities Public Review Webinar

Slide 17

Capability Email address/dissemination list Delivery notice Patient assent Management Patient Identification Topology System-to-System Portable Media System-to HIE-to-HIE Defining Content Component Service Collaboration Service Collaboration Marrying Content Definition with Secure Infrastructure for an arrangement of Interoperable data trades HITSP Capabilities Public Review Webinar

Slide 18

HITSP General Lab Orders Requirements and Design Public Comment Introduction & Review of Capabilities Schedule Technical Approach Public Comment HITSP Capabilities Public Review Webinar

Slide 19

Schedule Requirements for the General Lab Orders Extension/Gap acquainted with the Public by means of Webinar September 29, 2009 Comment input on the Requirements for this work thing closes October 8 th The procedure for submitting remarks is incorporated on slide 42 of this presentation The full archives will be discharged for a 4 week Public Comment period toward the beginning of November HITSP Capabilities Public Review Webinar

Slide 20

HITSP General Lab Orders Requirements and Design Public Comment Introduction & Review of Capabilities Schedule Technical Approach Public Comment HITSP Capabilities Public Review Webinar

Slide 21

Technical Approach of Capability 99 – Communicate Lab Order Message The Communicate Lab Order Message Capability fulfills the data trade necessities for the sending and accepting of an arrangement of research center request, control and status messages. Research facility requests might be from an inpatient or outpatient (e.g.,: Clinic, ER, office, and so on) environment This ability meets the necessities portrayed in the General Lab Orders Extension/Gap record by utilizing the HL7 2.51 Lab Order Messages, Tables 38 and 119 The Extension/Gap characterizes the accompanying prerequisites at an abnormal state: Review a posting of accessible requests Receive data/directions for requesting a general lab test Provide request subtle elements by utilizing pre-populated and/or physically populated fields inside a general lab request Provide extra data in regards to the lab request Modify and/or complete a lab request View the status of a lab arrange Unambiguously relate a request to a test outcome HITSP Capabilities Public Review Webinar

Slide 22

Technical Approach of Capability 99 Section 6 Information Exchanges are recognized from the useful necessities depicted in the 2009 General Lab Orders expansion/crevice report from ONC Interfaces are characterized by HL7 2.5.1 Non-Medical Orders Message Table 38 (States) and 119 (Control Commands) Existing builds are utilized for approval and transport another develop is required for control summons and status another develop is required for inventory administration HITSP Capabilities Public Review Webinar

Slide 23

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 24

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 25

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 26

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 27

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 28

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 29

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 30

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 31

Technical Approach of Capability 99 Section 6 HITSP Capabilities Public Review Webinar

Slide 32

Notional Laboratory Order Workflow HITSP Capabilities Public Review Webinar

Slide 33

Notional Lab Order States HITSP Capabilities Public Review Webinar

Slide 34

External Interfaces of Capability Technical Approach – Capability 99 Section 2 HITSP Capabilities Public Review Webinar

Slide 35

External Interfaces of Capability Technical Approach – Capability 99 Section 2 HITSP Capabilities Public Review Webinar

Slide 36

Questions for Public Comment The Extension/Gap expresses the need to alter a lab request Should this be finished by giving a change lab request interface, or by dropping and resending the request What do you do with examples that have as of now been gathered What are the state laws and strategies that identify with adjusting, stopping and scratching off requests Should this interface be required, discretionary or non existent If required, if it be actualized by remarks or organized/coded information There is some worry among SMEs whether a standing ord

Recommended
View more...