...
- Submit template change requests to PMO@HL7.org
- For Reaffirmations, please refer to the FAQ in Hl7 Project Scope Statement Instructions for a list of which sections and fields should be completed
Project Name and ID
Support for Automated Dispensing Cabinet Updates to HIS floor stock table | ||||||||||
Enter the name of the project here: | ||||||||||
| Project ID: | An ID will be assigned by Project Insight | |||||||||
Complete this section for all “Direct to Normative” ballot projects and when a project proceeds from “Informative to Normative” or “STU to Normative”. Forward PSS to the TSC (via tscpm@HL7.org); this triggers American National Standards Institute (ANSI) Project Initiation Notification (PINS) submission. | ||||||||||
| TSC Notification: Informative/STU to Normative | Date: Submission date | ||||||||
| - or - Direct to Normative (no STU) (includes reaffirmations) | 02/28/2019 | ||||||||
Identify ISO, IEC or ISO/IEC standard to be adopted in text box below | ||||||||||
Enter info here if an ISO, IEC, or ISO/IEC Standard is to be adopted as an American National Standard; Enter the designation of the standard(s) to be adopted: | ||||||||||
Includes text from ISO, IEC or ISO/IEC standard: Check here if this standard includes excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption. | Yes |
| No | |||||||
Select the unit of measure used in the standard; if no measurements are in the standard, select N/A |
| N/A |
| U.S. | Metric |
| Both | |||
| Investigative Project (aka PSS-Lite) | Date : | ||||||||
Check this box when the project is investigative or exploratory in nature, which allows limited project scope definition. Sections 1-Project Name, 2-Sponsoring Group(s)/Project Team, 3a-Project Scope, 3b-Project Need, 3e-Project Objectives/Deliverables/Target Dates, 3i-Project Document Repository, 6b-[Realm, if known], and 6d-[applicable Approval Dates] are required for Investigative Project. Investigative Project specific instructions are highlighted in yellow. An investigative project must advance in two WGM cycles, requiring a full scope statement. Otherwise the project will be closed. | ||||||||||
...
Primary Sponsor/Work Group | Pharmacy |
2.b. Co-sponsor Work Group(s)
...
Project facilitator (1Mandatory) | Dennis Tribble |
Other interested parties and their roles | |
Multi-disciplinary project team (recommended) | |
Modeling facilitator | |
Publishing facilitator | |
Vocabulary facilitator | Enter a name here (or ask Vocab for a name): |
Domain expert rep | |
Business requirement analyst | |
Conformance facilitator (for IG projects) | |
Other facilitators (SOA, etc) | |
Implementers (2Mandatory for STU projects) FHIR Project Note: The implementer requirement will be handled by the “balloting” project. Therefore work groups do not fill out the above section. However, feel free to list implementers specific to your work group’s resources if you know of any. | |
1) | |
2) | |
3. Project Definition
3.a. Project Scope
...
Describe the project; include what is expected to be accomplished/delivered along with specified features and functions. Include whether the deliverable(s) are universal, realm specific or applicable to various realms. Be sure to spell out all acronyms as these are carried forward to the NIB (Notice of Intent to Ballot) for ballot announcements..
3.b. Project Need
This information is required by ANSI for all ballots. Briefly explain the reason behind the need for this project. This may be related to legislative requirements, industry need, or similar justifications. |
Definition of triggers and content in support of interaction between healthcare information systems (HIS) and automated dispensing cabinet systems (ADC). Specifically, the HIS maintains a "floor stock" table that permits it to know whether or not a pharmacy dispense will be required for a new or changed medication order. This table maintains a list of the medications that are "floor stock" (that is, stored in an automated dispensing cabinet) on a particular nursing unit, and a list of the patient rooms on that unit. Using this table, the HIS can determine whether the pharmacy needs to dispense medication in response to a new or changed order based on whether or not that medication is already available in one or more automated dispensing cabinets that service that unit. The list of medications stored is incremented based on a "load" event (placement of a new medication into the cabinet) or an "unload" event (removal of a medication supply from the cabinet). As a result of such events, the ADC system must notify the HIS that its floor stock table must be updated. Typically, these interactions also provide information on the current inventory of the medication in the cabinet(s) serving a particular nursing unit, and the location(s) within the cabinet(s) where those medications may be loaded. This information permits electronic Medication Administration Records (eMAR) published by the HIS to inform the nurse where medications are located. Messages from the ADC to the HIS may therefore be generated any time the inventory within a cabinet is incremented (refilled, or loaded) or decremented (dispence from cabinet, unload from cabinet). |
3.b. Project Need
Current HL7 transactional systems do not support this interaction use case. The result is that these interactions are maintained in version 2.x HL7 messages using non-standard segments (Z-segments). The result of this implementation is that health systems that either change out HIS products (host conversions) or ADC systems are required to purchase and implement new interfaces at significant costs in both money and time. Standardizing these interactions would remove some, but not all, of the effort associated with such changes. |
3.c. Security Risks
Will this project produce executable(s), for example, schemas, transforms, style sheets, executable program, etc. If so the project must review and document security risks. Refer to the Cookbook for Security Considerations for additional guidance, including sample spreadsheets that may be used to conduct the security risk assessment. | Yes | |
X | No | |
Unknown |
3.d. External Drivers
...
Are the items being produced by this project backward compatible? | Yes | No | X | Unknown | N/A | |||
If you check 'Yes' please indicate the earliest prior release and/or version to which the compatibility applies: | ||||||||
For V3, are you using the current data types? (Refer to TSC position statement on new projects using R2B for more information on the current V3 data types) | X | Yes | No | Unknown | N/A | |||
If you check no, please explain the reason: | ||||||||
If desired, enter additional information regarding Backwards Compatibility. | ||||||||
...
Will this project include/reference external vocabularies? | Yes | No | X | Unknown | N/A | |||
If Yes, please enter the vocabularies: | ||||||||
...
| Stakeholders |
| Vendors |
| Providers | |
| Clinical and Public Health Laboratories | X | Pharmaceutical |
| Clinical and Public Health Laboratories | |
| Immunization Registries | X | EHR, PHR |
| Emergency Services | |
| Quality Reporting Agencies |
| Equipment |
| Local and State Departments of Health | |
| Regulatory Agency |
| Health Care IT |
| Medical Imaging Service | |
| Standards Development Organizations (SDOs) |
| Clinical Decision Support Systems | X | Healthcare Institutions (hospitals, long term care, home care, mental health) | |
| Payors |
| Lab |
| Other (specify in text box below) | |
| Other (specify in text box below) | X | HIS |
| N/A | |
| N/A |
| Other (specify below) |
| ||
|
| N/A |
|
| ||
Other: Indicate other stakeholders, vendors or providers not listed above. | ||||||
...