Page tree

StatusReady for implementation
Version

1.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase Significance
Product containing precisely [substance][number][Numerator Unit of measure ]/[1][Denominator Unit of measure ] [dose form] (clinical drug)FSNus:Pgb:Pci
[substance] [number] [Numerator Unit of measure ]/ [Denominator Unit of measure ] [dose form] (clinical drug)SYNus:Pgb:Pci


Concept model:

Definition status:  

900000000000073002 |Defined (core metadata concept)|

Applies To:


<<   763158003 |Medicinal product (product)|   :   411116001 |Has manufactured dose form (attribute)|   = <   736542009 |Pharmaceutical dose form (dose form)|  ,  { 733725009 |Has concentration strength numerator unit (attribute)|  = <  767524001 |Unit of measure (qualifier value)| }

Template Language


Rules for description generation:

  1. Apply General rules for generating descriptions for templates
  2. For multiple ingredients, the BoSS substance ingredients in each description need to be in alphabetical order 

  3. For the FSN; align terming and case sensitivity with the FSN for the concepts that are selected as the attribute values, excluding the semantic tag e.g. Product containing precisely clotrimazole 10 milligram/1 gram conventional release cutaneous cream (clinical drug)
  4. For the PT; align terming and case sensitivity with the PT for the concepts that are selected as the attribute values e.g. Clotrimazole 10 mg/g cutaneous cream
  5. For multiple ingredients, for FSN add 'and [substance][number][Unit of measure ]' after the first [substance][number][Unit of measure ] for each  |Has basis of strength substance (attribute)| Example: 
    Product containing precisely lopinavir 80 milligram/1 milliliter and ritonavir 20 milligram/1 milliliter conventional release oral solution (clinical drug)

  6. For multiple ingredients PT - add ' [substance][number][Unit of measure ] and' at the beginning of the PT Example;  Lopinavir 80 mg/mL and ritonavir 20 mg/mL oral solution

  7. FSN Exceptions: If substance value for Precise active ingredient  <> BoSS add (as [substance]) to text string as illustrated below. The substance value in parentheses uses the substance value for the Precise active ingredient (PAA) and not the BoSS, which is the first substance value in the description: Single ingredient example  = Product containing precisely <BoSS FSN> (as <Precise active ingredient FSN>) <Concentration strength numerator value FSN> <Concentration strength numerator unit FSN>/<Concentration strength denominator value FSN> <Concentration strength denominator unit FSN> <Manufactured dose form FSN> (clinical drug)

    Examples:

    • Product containing precisely amikacin (as amikacin sulfate) 250 milligram/1 milliliter conventional release solution for injection (clinical drug)
      Product containing precisely mupirocin (as mupirocin calcium) 20 milligram/1 gram conventional release nasal ointment (clinical drug)

     PT Exceptions:                                                                                                                                                                                                                                                                                                                                                   
    Where BoSS <> Precise active ingredient: Single ingredient example

    <BoSS PT> (as <Precise active ingredient PT>) <Concentration strength numerator value PT> <Concentration strength numerator unit PT>/<Concentration strength denominator value PT> <Concentration strength denominator unit PT> <Manufactured dose form PT>

    Example:

    Amikacin (as amikacin sulfate) 250 mg/mL solution for injection
    Mupirocin (as mupirocin calcium) 20 mg/g nasal ointment

7. The following units of measure should not be abbreviated in descriptions; they should always be spelled out: international unit, microgram, million unit, nanogram, picogram, unit


Jira tickets:

DRUGS-548 - Getting issue details... STATUS

DRUGS-646 - Getting issue details... STATUS

/browse/INFRA-12578




5 Comments

  1. Yongsheng Gao this template is ready for your review. Thanks.

  2. Yongsheng Gao this Template version 0.9 is ready for your review and forward to the technical team.

    As discussed you will update  < 260299005 |Number (qualifier value)| and    
    38112003 |1 (qualifier value)| to concrete domains and change Number in descriptions.

  3. Hi Yongsheng Gao updated to concrete domain - wasn't sure if 733723002 |Has concentration strength denominator value (attribute)| is correctly represented as just 1 (or is it #1).

    Sonja has indicated "Please note that the deadline for development cutoff for the upcoming release is March 7. To ensure that any updates to the template are included, please complete the specification a few days prior to this date." So will go through all of them and update in the same way to save time.

    1. Hi Nicola Ingram  the value for denominator should be  #1.  I have completed update of template CD-precise discrete dose form (clinical drug) - v1.0 . Could you please update other templates accordingly?

      Note, attributes for concrete values have been inactived and replaced by the new data attributes. They need to be updated to active attributes.