Package org.hl7.fhir.r5.profilemodel.gen
Class ProfileExample
java.lang.Object
org.hl7.fhir.r5.profilemodel.gen.PEGeneratedBase
org.hl7.fhir.r5.profilemodel.gen.ProfileExample
This class is a manually written example of the code that a POJO code
generator for Profiles would produce
Should you generate code? If you can bind at compile time, then you should.
If you can't - and most systems can't, given the nature of profiles, then
you should use PEInstance directly
- Author:
- grahamegrieve
-
Nested Class Summary
Modifier and TypeClassDescriptionstatic enum
static class
static class
-
Field Summary
Fields inherited from class org.hl7.fhir.r5.profilemodel.gen.PEGeneratedBase
instance, workerContext
-
Constructor Summary
ConstructorDescriptionProfileExample
(IWorkerContext context, Observation observation) ProfileExample
(PEInstance instance) this is public for testing purposes, but you generally shouldn't use it. -
Method Summary
Modifier and TypeMethodDescriptiongetCode()
Extension http://hl7.org/fhir/test/StructureDefinition/pe-extension-simple, type codeboolean
boolean
Methods inherited from class org.hl7.fhir.r5.profilemodel.gen.PEGeneratedBase
getData, getInstance, removeChild, removeChildren
-
Constructor Details
-
ProfileExample
-
ProfileExample
this is public for testing purposes, but you generally shouldn't use it. If you do, make sure the parameters are (PEElementPropertiesPolicy.EXTENSION_ID, true) when building the PEBuilder- Parameters:
instance
-
-
-
Method Details
-
getStatus
- Returns:
- fixed value "final"
-
getCode
-
getSimple
Extension http://hl7.org/fhir/test/StructureDefinition/pe-extension-simple, type code- Returns:
-
hasSimple
-
clearSimple
-
getComplex
-
hasComplex
-
clearComplex
-