Render overview

The { { render: project name / url-key } } statement enables you to quickly render almost all resource's overview tabs in your Implementation guide. For example StructureDefinitions, OperationDefinitions or Images.

1. List of resources

Here I describe the resources in my Guide.

idΣ0..1id
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionC0..*Extension
modifierExtension?! C0..*Extension
identifierΣ0..*Identifier
basedOnΣ C0..0Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest)
partOfΣ C0..1Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy)
statusS Σ ?!1..1codeBinding
category0..*CodeableConceptBinding
id0..1
extensionC0..*Extension
id0..1
extensionC0..*Extension
systemS Σ1..1uriFixed Value
versionΣ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
textΣ0..1string
subjectS Σ C1..1Reference(DevDaysIGtutorial-Patient)
focusΣ C0..*Reference(Resource)
encounterΣ C0..1Reference(Encounter)
effectiveDateTimeS Σ1..1dateTime, Period, Timing, instant
issuedΣ0..1instant
performerΣ C0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson)
id0..1
extensionC0..*Extension
valueS Σ1..1decimal
comparatorΣ ?!0..1codeBinding
unitS Σ1..1string
systemS Σ C1..1uriFixed Value
codeS Σ1..1code
dataAbsentReasonS C0..1CodeableConceptBinding
interpretation0..*CodeableConceptBinding
note0..*Annotation
bodySite0..0CodeableConcept
id0..1
id0..1
extensionC0..*Extension
url1..1Fixed Value
methodQualifier1..1CodeableConceptBinding
id0..1
extensionC0..*Extension
systemΣ1..1uri
versionΣ0..1string
codeΣ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
textΣ0..1string
specimenC0..1Reference(Specimen)
deviceC0..0Reference(Device | DeviceMetric)
id0..1
extensionC0..*Extension
modifierExtensionΣ ?! C0..*Extension
lowC0..1SimpleQuantity
highC0..1SimpleQuantity
type0..1CodeableConceptBinding
appliesTo0..*CodeableConcept
ageC0..1Range
text0..1string
hasMemberΣ C0..0Reference(Observation | QuestionnaireResponse | MolecularSequence)
derivedFromΣ C0..0Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence)

2. OperationDefinition

Besides StructureDefinition, the render statement can be used for other resources as well. OperationDefinition resources for example.

Invocations

URL: [base]/ActivityDefinition/[id]/$data-requirements

Return Values (Out)

NameCardinalityTypeDocumentation
return1..1Library

The result of the requirements gathering represented as a module-definition Library that describes the aggregate parameters, data requirements, and dependencies of the activity definition

The effect of invoking this operation is to determine the aggregate set of data requirements and dependencies for the activity definition. The result is a Library resource with a type of module-definition that contains all the parameter definitions and data requirements of the activity definition and any libraries referenced by it. Implementations SHOULD aggregate data requirements intelligently (i.e. by collapsing overlapping data requirements)

example for search parameter

Invocations

[base]/Observation?method-qualifier=[system]|[value]

Details

ResourceObservation
Codemethod-qualifier
Typetoken
FhirPathObservation.method.extension('http://devdays-example-ig.com/fhir/StructureDefinition/DevDaysIGtutorial-observation-method-qualifier')