<<

SACC

Standards and Convention Committee

Safety Stock

The quantity of an inventory item that is kept in an inventory location for Patient safety purposes in order to allow for deviations in demand or supply that might stem from variability in internal processes, unforeseen Patient demand, supplier availability, or transportation.

SAML

Security Assertion Markup Language

SC

Steering Committee

SCCB

SwRI Configuration Control Board

Schedule

The frequency by which the doses are to be administered (i.e., Q8H, BID, NOW). Often referred to as Administration Schedule.

Schedule Type

The indicator that identifies the type of schedule (i.e., Continuous, PRN, On-Call, and One-Time) for the medication being administered to a Patient.

Scheduled Order

An Inpatient order that is scheduled to be delivered to a ward at a specific time. Scheduled orders appear in a Unit Dose Pick List or Sterile Product Work List for filling.

SCM

Software Configuration Management

Scored

Indicates that the medication has been marked by the manufacturer so that the medication can be divided (e.g., split) in two.

SDD

Software Design Document

SDF

Software Development Folder

SDK

Software Development Kit

SDLC

Software Development Life Cycle

SDS

Standard Data Service

Secondary Inventories

The stock that is maintained in user areas.

Section 508

The section of the Rehabilitation Act that requires any electronic information developed, procured, maintained, or used by the federal government be accessible to people with disabilities. As a result of new requirements added to the Rehabilitation Act in 1998, guidelines for electronic information including Web sites have been developed and were adopted on December 21, 2000. All electronic information created or acquired by any federal agency or department, on or after June 21, 2001, must comply with these accessibility standards.

SEO

Software Engineering Organization

Sequence Diagram

A visual representation that shows interaction between objects with an emphasis on the order in which the objects pass information or actions between themselves. The objects could be (i.e., people, computer systems, locations, etc.).

Service

A logical grouping of capabilities that support a common business process. Thus a “drug information service” might provide capabilities that allow for the searching of different types of drug information and different types of searches for the same information (i.e., searching for a drug by Generic Name, NDC, Therapeutic category). This is loosely analogous to the class-method relationship, in which a class is composed of multiple methods that support the usage of the class.

Service (Architecture)

A logical grouping of related software capabilities that share common business goals in a functional process and communicate through a well-defined interface mechanism.

Service-Oriented Architecture (SOA)

A system architecture that encourages the development, collection and use of software services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating to complete an activity. Services require a standardized communication protocol.

Session Bean

A reusable software component that is used to implement business logic; it can be of stateless or stateful variety; its existence is short-lived; and its purpose is to execute on behalf of a single client.

Session Facade

Decouples the user of the service from the multiple entity beans that may reside behind a service method by providing a common session bean for that particular service. For example, most service method calls will require two distinct events to complete: one to authenticate that the user is authorized to use the service, and the second is to invoke the capability of the service method. It hides these event invocations from the client, providing them with one session bean that handles all subsequent method invocations required to complete the service method request.

SGML

Standard Generalized Markup Language

SHG

Strategic Health Group

Shortage

A deficit between inventory available and inventory required.

SIG

The Latin word, Signatura, abbreviated as “SIG.” (also called SIG, or transcription), which gives instructions to the Patient on how, how much, when, and how long the drug is to be taken. These written instructions are preceded by the symbol “S” or “SIG.” from the Latin, meaning “mark.” The signature should always be written in English; however, Physicians continue to insert Latin abbreviations, e.g., “1 cap t.i.d. pc,” which the Pharmacist translates into English when he or she prints the label, such as “take one capsule three times daily after meals.” The purpose of the prescription, special instructions, and warnings, followed by the signature of the prescriber, may also be included.

Sign Order

The action taken by a user to provide a signature on an order that is legally binding. In the system, the signature is an electronic signature. See glossary term Electronic Signature.

SIL

Security Integration Laboratory

Simple Object Access Protocol (SOAP)

A lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML-based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined data types, and a convention for representing remote procedure calls and responses.

Single Sign-On

A set of software components, usually distributed over a network, which allow a user to log into his workstation once, and thereafter start applications without having further authentication required.

Smart Card

In the VA/DEA PKI Pilot, the clinician uses a smart card to digitally sign Outpatient medication orders for Schedule 2 and Schedule 2n CS after using the current electronic signature process within CPRS. The technologies used in PKI add security for these substances. Smart cards have the clinician’s photo and an integrated circuit (a computer chip) that stores other information such as demographics, access and verity codes, a personal identification number (PIN), and a digital certificate.

SME

Stakeholder/Subject Matter Expert

SOA

Service Oriented Architecture

SOAP

Simple Object Access Protocol

Software Configuration Management (SCM)

A process or methodology comprised of tools and techniques that are used to manage change to software assets.

Software Development Kit (SDK)

A set of tools, APIs, and/or documentation to assist with the development of software in a specific computer language or for a particular operating environment.

Software Development Life Cycle (SDLC)

A structured methodology used in the development of software products and packages. This methodology is used from the conception phase through to the delivery and end of life of a final software product.

Software Development Plan (SDP)

A comprehensive, composite artifact that gathers all information required to manage the project. It encompasses a number of artifacts developed during the Initiation phase and is maintained throughout the project.

Software Package

A software term for a high-level, common grouping of one or more components within a system.

Software Quality Assurance (SQA)

The set of activities that defines and implements software quality into the process and encompasses systematic activities that provide evidence that the product meets the customer’s expectations, in terms of use and the associated quality factors. This includes monitoring the methods and standards used, and then verifying that they have been properly applied. Also tracks that the required procedures have taken place during the SDLC. It does this by auditing the quality actions of the products in development and alerting management to any deviations.

Software Quality Assurance Team

Oversees all aspects of quality assurance in each OED project.

Software Requirements Specifications (SRS)

A document that outlines and records the requirements for a project. The document formally states the requirements for the project.

Solution

A vehicle for additive(s) or for the pharmacological effect of the solution itself. Infusion is generally continuous. A LVP or piggyback has only one solution (primary solution). A hyperal can have one or more solutions.

SOP

Standard Operating Procedure

SOW

Statement of Work

Special Handling

The Drug Enforcement Agency (DEA) special handling codes used to designate drug products as over-the-counter, narcotics, bulk compounds, supply items. Requirements exist for each code that determines how a drug product is to be handled and/or stored.

Specialty

The particular subject area or branch of medical science to which one devotes professional attention.

SPF

Single Point of Failure

Splittable

A VA Data Field used to specify whether an item can be split for dispense or be prescribed as a splittable dose.

SPM

Software Project Manager

SPML

Service Provisioning Markup Language

SQA

Software Quality Assurance

SQAP

Software Quality Assurance Plan

SQL

Structured Query Language

SRS

Software Requirements Specification

SS

System Specification

SSO

Single Sign-On

Staging Area

A specific inventory location where items slated for disposal are placed prior to shipping or destruction. This is for control and tracking of items removed from active inventories for reasons such as product quality, spoilage, expirations, or recalls.

Stakeholders

The people or groups who have a stake in the outcome of the project. Normally stakeholders are from within the company (e.g., internal clients, management, employees, administrators). A project may also have external stakeholders, including suppliers, investors, community groups, and government organizations.

Standard Data Service (SDS)

Consists of architecture service components to support the migration of applications from M-based VistA to new HealtheVet-VistA architecture. The major purpose of SDS is to provide a centralized repository of standard (non-clinical) administrative data together with a data maintenance mechanism and a distribution capability for transporting the data to HealtheVet-VistA applications.

Standardized Domain

Domains are standard or standardized. Standardized domains will have a VUID from VETS, using the specified field(s) for that item or domain to determine the uniqueness of the VUID.

STAT

Statim (Latin: Immediately [medical])

Steering Committee (SC)

The key body within the governing structure that is responsible for the business issues associated with the project that are essential to ensuring the delivery of the project outputs and the attainment of project outcomes. This includes approving the budgetary strategy, defining and realizing benefits, monitoring risks, quality and timelines, making policy and resourcing decisions, and assessing requests for changes to the scope of the project.

Sterile Product

An item that is completely clean and free from bacteria (e.g., IVs and gauzes).

Sterile Product Work List

A list of sterile product Dispense Requests that are scheduled to be administered to the Patients in a ward group within a specified window of time. The Sterile Product Work List replaces the ward list and manufacturing list from VistA.

Stock Level

The current inventory quantity of an item. It may be a calculated or physical count quantity depending on the use in the system. It may also be displayed and used at multiple organizational levels such as a quantity in a specific inventory location, the quantity in a ward, the quantity in central pharmacy supply, or a total rolled up quantity for the entire facility.

Storage Location

Where the contents of a Dispense Request are stored. Once a Dispense Request product is filled and checked, it is stored in a designated Storage Location to be later retrieved by the Medication Deliverer at the window or in the mail room. The Storage Location could be a particular refrigeration unit if the medication needs to be kept cool, a locked cage in the case of CS, or a tote for those medications that need to be packaged and mailed.

Structural Testing

Testing that takes into account the internal mechanism of a system or component.

STS

Standards and Terminology Services

Stub

A piece of code used during development to simulate the activity of a missing service, component, or interface that is not yet developed.

Subject Matter Expert

A person thought of as dictionaries or references that provide the final authority on what something means or how it is to be performed, while developers and trainers are the readers who turn that authority into information that can be understood and used by others. They are experts on the content of information.

Subsystem

A subsystem is a logical grouping of related software packages and services that combine to form an independent system within an enterprise.

Supply Area

The pharmacy inventory locations from which Patient orders are filled or user area requirements are replenished. It also is the area where incoming inventory is stocked following the receiving process from outside sources (e.g., vendors, loans, gifts).

Support Staff

A person who identifies Patients (or panel of Patients) who need to be seen or have requested to be seen.

SwRIa

Southwest Research Institute

Syringe

A device used to inject fluids into or withdraw them from something (e.g., the body or its cavities, IV set).

System Administrator

An authorized person who manages the components of the Pharmacy System to which access is restricted for most Pharmacy users. For example, a System Administrator might create user profiles, define local user roles, configure local parameters, or run reports.



>>