Resource overview

Almost all overview tabs of any resource can be rendered in your Implementation Guide. StructureDefinitions have their own tree statement for this, other resources use the render statement.

StructureDefinition

This is the StructureDefinition overview for the us-core-patient resource in the demo project. You can find the resource on https://simplifier.net/demo/us-core-patient-2. Notice that the path in the URL is exactly the same as the placeholder.

Differential

There is no placeholder called ''

Hybrid

raceS I0..1Extension
ethnicityS I0..1Extension
birthsexS I0..1ExtensionBinding
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemS Σ1..1uri
valueS Σ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
activeΣ ?!0..1boolean
useΣ ?!0..1codeBinding
textΣ0..1string
familyS Σ1..1string
givenS Σ1..*string
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period
telecomΣ I0..*ContactPoint
genderS Σ1..1codeBinding
birthDateS Σ0..1date
deceasedBooleanboolean
deceasedDateTimedateTime
addressΣ0..*Address
maritalStatus0..1CodeableConceptBinding
multipleBirthBooleanboolean
multipleBirthIntegerinteger
photoI0..*Attachment
relationship0..*CodeableConceptBinding
name0..1HumanName
telecomI0..*ContactPoint
address0..1Address
gender0..1codeBinding
organizationI0..1Reference(Organization)
periodI0..1Period
languageS1..1CodeableConceptBinding
preferred0..1boolean
generalPractitionerI0..*Reference(Organization | Practitioner)
managingOrganizationΣ I0..1Reference(Organization)
otherΣ I1..1Reference(Patient | RelatedPerson)
typeΣ1..1codeBinding

Snapshot (default)

raceS I0..1Extension
ethnicityS I0..1Extension
birthsexS I0..1ExtensionBinding
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemS Σ1..1uri
valueS Σ1..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
activeΣ ?!0..1boolean
useΣ ?!0..1codeBinding
textΣ0..1string
familyS Σ1..1string
givenS Σ1..*string
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period
telecomΣ I0..*ContactPoint
genderS Σ1..1codeBinding
birthDateS Σ0..1date
deceasedBooleanboolean
deceasedDateTimedateTime
addressΣ0..*Address
maritalStatus0..1CodeableConceptBinding
multipleBirthBooleanboolean
multipleBirthIntegerinteger
photoI0..*Attachment
relationship0..*CodeableConceptBinding
name0..1HumanName
telecomI0..*ContactPoint
address0..1Address
gender0..1codeBinding
organizationI0..1Reference(Organization)
periodI0..1Period
languageS1..1CodeableConceptBinding
preferred0..1boolean
generalPractitionerI0..*Reference(Organization | Practitioner)
managingOrganizationΣ I0..1Reference(Organization)
otherΣ I1..1Reference(Patient | RelatedPerson)
typeΣ1..1codeBinding

Other resources

The render statement (without spaces between the brackets) enables you to render all other resources. See the below OperationDefinition (from https://simplifier.net/core-opdefs-stu3/ActivityDefinition-data-requirements) resource as an 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)