FHIR CI-Build

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

Enrollmentrequest.shex

Financial Management Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Patient

Raw ShEx

ShEx statement for enrollmentrequest

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 <Patient.shex>
IMPORT <dateTime.shex>
IMPORT <Coverage.shex>
IMPORT <Reference.shex>
IMPORT <Identifier.shex>
IMPORT <Organization.shex>
IMPORT <Practitioner.shex>
IMPORT <DomainResource.shex>
IMPORT <PractitionerRole.shex>

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

# Enroll in coverage
<EnrollmentRequest> EXTENDS @<DomainResource> CLOSED {   
    a [fhir:EnrollmentRequest]?;fhir:nodeRole [fhir:treeRoot]?;

    fhir:identifier @<OneOrMore_Identifier>?;  # Business Identifier
    fhir:status @<code> AND
    	{fhir:v @fhirvs:fm-status}?;  # active | cancelled | draft | 
                                            # entered-in-error 
    fhir:created @<dateTime>?;              # Creation date
    fhir:insurer @<Reference> AND {fhir:link 
    			@<Organization> ? }?;  # Target
    fhir:provider @<Reference> AND {fhir:link 
    			@<Organization> OR 
    			@<Practitioner> OR 
    			@<PractitionerRole> ? }?;  # Responsible practitioner
    fhir:candidate @<Reference> AND {fhir:link 
    			@<Patient> ? }?;  # The subject to be enrolled
    fhir:coverage @<Reference> AND {fhir:link 
    			@<Coverage> ? }?;  # Insurance information
}  

#---------------------- Cardinality Types (OneOrMore) -------------------
<OneOrMore_Identifier> CLOSED {
    rdf:first @<Identifier>  ;
    rdf:rest [rdf:nil] OR @<OneOrMore_Identifier> 
}

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

# This value set includes Status codes.
fhirvs:fm-status ["active" "cancelled" "draft" "entered-in-error"]


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.