FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Formularyitem.shex

Pharmacy Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

Raw ShEx

ShEx statement for formularyitem

PREFIX fhir: <http://hl7.org/fhir/> 
PREFIX fhirvs: <http://hl7.org/fhir/ValueSet/>
PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> 
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> 

IMPORT <code.shex>
IMPORT <Identifier.shex>
IMPORT <DomainResource.shex>
IMPORT <CodeableConcept.shex>


start=@<FormularyItem> AND {fhir:nodeRole [fhir:treeRoot]}

# Definition of a FormularyItem
<FormularyItem> EXTENDS @<DomainResource> CLOSED {   

    a [fhir:FormularyItem]?;
    fhir:nodeRole [fhir:treeRoot]?;

    fhir:identifier @<OneOrMore_Identifier>?;  # Business identifier for this 
                                            # formulary item 
    fhir:code @<CodeableConcept>?;          # Codes that identify this formulary 
                                            # item 
    fhir:status @<code> AND
    	{fhir:v @fhirvs:formularyitem-status}?;  # active | entered-in-error | 
                                            # inactive 
}  

#---------------------- Cardinality Types (OneOrMore) -------------------

<OneOrMore_Identifier> CLOSED {
    rdf:first @<Identifier>  ;
    rdf:rest [rdf:nil] OR @<OneOrMore_Identifier> 
}

#---------------------- Value Sets ------------------------

# FormularyItem Status Codes
fhirvs:formularyitem-status ["active" "entered-in-error" "inactive"]


Usage note: every effort has been made to ensure that the ShEx files are correct and useful, but they are not a normative part of the specification.