HL7.TERMINOLOGY\FirstFillPharmacySupplyType

HL7 Terminology (THO)
3.0.0 - Publication

This page is part of the HL7 Terminology (v3.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: FirstFillPharmacySupplyType

Summary

Defining URL:

http://terminology.hl7.org/ValueSet/v3-FirstFillPharmacySupplyType

Version:

2.0.0

Name:

FirstFillPharmacySupplyType

Status:

Active as of 3/26/14

Definition:

The initial fill against an order. (This includes initial fills against refill orders.)

OID:

2.16.840.1.113883.1.11.16209 (for OID based terminology systems)

Source Resource:

XML / JSON / Turtle

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Include codes from http://terminology.hl7.org/CodeSystem/v3-ActCode where concept is-a FF

Expansion

This value set contains 9 concepts

Expansion based on ActCode v6.0.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/v3-ActCode

Code	Display	Definition
FF	First Fill	The initial fill against an order. (This includes initial fills against refill orders.)
FFS	fee for service	A billing arrangement where a Provider charges a separate fee for each intervention/procedure/event or product. Fee for Service is used when an individual intervention/procedure/event is used for billing purposes. In other words, fees are associated with the intervention/procedure/event. For example, a specific CCI (Canadian Classification of Interventions) code has an associated fee and is used for billing purposes.
FFPS	first fill, part fill, partial strength	A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets)
FFCS	first fill complete, partial strength	A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets) and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets).
TFS	trial fill partial strength	A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance and also where the strength supplied is less than the ordered strength (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets).
FFC	First Fill - Complete	A first fill where the quantity supplied is equal to one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a complete fill would be for the full 90 tablets).
FFP	First Fill - Part Fill	A first fill where the quantity supplied is less than one full repetition of the ordered amount. (e.g. If the order was 90 tablets, 3 refills, a partial fill might be for only 30 tablets.)
FFSS	first fill, partial strength	A first fill where the strength supplied is less than the ordered strength. (e.g. 10mg for an order of 50mg where a subsequent fill will dispense 40mg tablets).
TF	Trial Fill	A fill where a small portion is provided to allow for determination of the therapy effectiveness and patient tolerance.

Explanation of the columns that may appear on this page:

Level

A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies

Source

The source of the definition of the code (when the value set draws in codes defined elsewhere)

Code

The code (used as the code in the resource instance)

Display

The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application

Definition

An explanation of the meaning of the concept

Comments

Additional notes about how to use the code

History

Date

Action

Author

Custodian

Comment

2020-05-06

revise