@medplum/fhirtypes 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (199) hide show
  1. package/README.md +61 -0
  2. package/dist/AccessPolicy.d.ts +95 -0
  3. package/dist/Account.d.ts +286 -0
  4. package/dist/ActivityDefinition.d.ts +580 -0
  5. package/dist/Address.d.ts +93 -0
  6. package/dist/AdverseEvent.d.ts +353 -0
  7. package/dist/Age.d.ts +60 -0
  8. package/dist/AllergyIntolerance.d.ts +329 -0
  9. package/dist/Annotation.d.ts +54 -0
  10. package/dist/Appointment.d.ts +330 -0
  11. package/dist/AppointmentResponse.d.ts +154 -0
  12. package/dist/Attachment.d.ts +74 -0
  13. package/dist/AuditEvent.d.ts +532 -0
  14. package/dist/Basic.d.ts +130 -0
  15. package/dist/Binary.d.ts +78 -0
  16. package/dist/BiologicallyDerivedProduct.d.ts +416 -0
  17. package/dist/BodyStructure.d.ts +142 -0
  18. package/dist/Bot.d.ts +64 -0
  19. package/dist/Bundle.d.ts +438 -0
  20. package/dist/CapabilityStatement.d.ts +1193 -0
  21. package/dist/CarePlan.d.ts +518 -0
  22. package/dist/CareTeam.d.ts +247 -0
  23. package/dist/CatalogEntry.d.ts +230 -0
  24. package/dist/ChargeItem.d.ts +338 -0
  25. package/dist/ChargeItemDefinition.d.ts +460 -0
  26. package/dist/Claim.d.ts +1269 -0
  27. package/dist/ClaimResponse.d.ts +1204 -0
  28. package/dist/ClientApplication.d.ts +61 -0
  29. package/dist/ClinicalImpression.d.ts +355 -0
  30. package/dist/CodeSystem.d.ts +627 -0
  31. package/dist/CodeableConcept.d.ts +43 -0
  32. package/dist/Coding.d.ts +63 -0
  33. package/dist/Communication.d.ts +309 -0
  34. package/dist/CommunicationRequest.d.ts +306 -0
  35. package/dist/CompartmentDefinition.d.ts +253 -0
  36. package/dist/Composition.d.ts +494 -0
  37. package/dist/ConceptMap.d.ts +596 -0
  38. package/dist/Condition.d.ts +379 -0
  39. package/dist/Consent.d.ts +529 -0
  40. package/dist/ContactDetail.d.ts +41 -0
  41. package/dist/ContactPoint.d.ts +60 -0
  42. package/dist/Contract.d.ts +1676 -0
  43. package/dist/Contributor.d.ts +48 -0
  44. package/dist/Count.d.ts +62 -0
  45. package/dist/Coverage.d.ts +380 -0
  46. package/dist/CoverageEligibilityRequest.d.ts +468 -0
  47. package/dist/CoverageEligibilityResponse.d.ts +507 -0
  48. package/dist/DataRequirement.d.ts +276 -0
  49. package/dist/DetectedIssue.d.ts +293 -0
  50. package/dist/Device.d.ts +570 -0
  51. package/dist/DeviceDefinition.d.ts +563 -0
  52. package/dist/DeviceMetric.d.ts +231 -0
  53. package/dist/DeviceRequest.d.ts +347 -0
  54. package/dist/DeviceUseStatement.d.ts +198 -0
  55. package/dist/DiagnosticReport.d.ts +294 -0
  56. package/dist/Distance.d.ts +60 -0
  57. package/dist/DocumentManifest.d.ts +229 -0
  58. package/dist/DocumentReference.d.ts +403 -0
  59. package/dist/Dosage.d.ts +184 -0
  60. package/dist/Duration.d.ts +59 -0
  61. package/dist/EffectEvidenceSynthesis.d.ts +686 -0
  62. package/dist/Element.d.ts +29 -0
  63. package/dist/ElementDefinition.d.ts +3010 -0
  64. package/dist/Encounter.d.ts +643 -0
  65. package/dist/Endpoint.d.ts +166 -0
  66. package/dist/EnrollmentRequest.d.ts +135 -0
  67. package/dist/EnrollmentResponse.d.ts +140 -0
  68. package/dist/EpisodeOfCare.d.ts +286 -0
  69. package/dist/EventDefinition.d.ts +297 -0
  70. package/dist/Evidence.d.ts +295 -0
  71. package/dist/EvidenceVariable.d.ts +431 -0
  72. package/dist/ExampleScenario.d.ts +728 -0
  73. package/dist/ExplanationOfBenefit.d.ts +2140 -0
  74. package/dist/Expression.d.ts +58 -0
  75. package/dist/Extension.d.ts +365 -0
  76. package/dist/FamilyMemberHistory.d.ts +359 -0
  77. package/dist/Flag.d.ts +155 -0
  78. package/dist/Goal.d.ts +345 -0
  79. package/dist/GraphDefinition.d.ts +408 -0
  80. package/dist/Group.d.ts +315 -0
  81. package/dist/GuidanceResponse.d.ts +228 -0
  82. package/dist/HealthcareService.d.ts +415 -0
  83. package/dist/HumanName.d.ts +73 -0
  84. package/dist/Identifier.d.ts +67 -0
  85. package/dist/ImagingStudy.d.ts +472 -0
  86. package/dist/Immunization.d.ts +520 -0
  87. package/dist/ImmunizationEvaluation.d.ts +179 -0
  88. package/dist/ImmunizationRecommendation.d.ts +298 -0
  89. package/dist/ImplementationGuide.d.ts +944 -0
  90. package/dist/InsurancePlan.d.ts +719 -0
  91. package/dist/Invoice.d.ts +399 -0
  92. package/dist/JsonWebKey.d.ts +126 -0
  93. package/dist/Library.d.ts +324 -0
  94. package/dist/Linkage.d.ts +170 -0
  95. package/dist/List.d.ts +236 -0
  96. package/dist/Location.d.ts +324 -0
  97. package/dist/Login.d.ts +146 -0
  98. package/dist/MarketingStatus.d.ts +96 -0
  99. package/dist/Measure.d.ts +715 -0
  100. package/dist/MeasureReport.d.ts +531 -0
  101. package/dist/Media.d.ts +243 -0
  102. package/dist/Medication.d.ts +267 -0
  103. package/dist/MedicationAdministration.d.ts +403 -0
  104. package/dist/MedicationDispense.d.ts +398 -0
  105. package/dist/MedicationKnowledge.d.ts +1136 -0
  106. package/dist/MedicationRequest.d.ts +554 -0
  107. package/dist/MedicationStatement.d.ts +262 -0
  108. package/dist/MedicinalProduct.d.ts +530 -0
  109. package/dist/MedicinalProductAuthorization.d.ts +320 -0
  110. package/dist/MedicinalProductContraindication.d.ts +199 -0
  111. package/dist/MedicinalProductIndication.d.ts +210 -0
  112. package/dist/MedicinalProductIngredient.d.ts +391 -0
  113. package/dist/MedicinalProductInteraction.d.ts +186 -0
  114. package/dist/MedicinalProductManufactured.d.ts +135 -0
  115. package/dist/MedicinalProductPackaged.d.ts +305 -0
  116. package/dist/MedicinalProductPharmaceutical.d.ts +383 -0
  117. package/dist/MedicinalProductUndesirableEffect.d.ts +121 -0
  118. package/dist/MessageDefinition.d.ts +384 -0
  119. package/dist/MessageHeader.d.ts +374 -0
  120. package/dist/Meta.d.ts +92 -0
  121. package/dist/MolecularSequence.d.ts +875 -0
  122. package/dist/Money.d.ts +39 -0
  123. package/dist/NamingSystem.d.ts +255 -0
  124. package/dist/Narrative.d.ts +42 -0
  125. package/dist/NutritionOrder.d.ts +650 -0
  126. package/dist/Observation.d.ts +601 -0
  127. package/dist/ObservationDefinition.d.ts +326 -0
  128. package/dist/OperationDefinition.d.ts +542 -0
  129. package/dist/OperationOutcome.d.ts +186 -0
  130. package/dist/Organization.d.ts +217 -0
  131. package/dist/OrganizationAffiliation.d.ts +172 -0
  132. package/dist/ParameterDefinition.d.ts +72 -0
  133. package/dist/Parameters.d.ts +388 -0
  134. package/dist/PasswordChangeRequest.d.ts +66 -0
  135. package/dist/Patient.d.ts +398 -0
  136. package/dist/PaymentNotice.d.ts +162 -0
  137. package/dist/PaymentReconciliation.d.ts +330 -0
  138. package/dist/Period.d.ts +42 -0
  139. package/dist/Person.d.ts +206 -0
  140. package/dist/PlanDefinition.d.ts +968 -0
  141. package/dist/Population.d.ts +76 -0
  142. package/dist/Practitioner.d.ts +223 -0
  143. package/dist/PractitionerRole.d.ts +302 -0
  144. package/dist/Procedure.d.ts +432 -0
  145. package/dist/ProdCharacteristic.d.ts +132 -0
  146. package/dist/ProductShelfLife.d.ts +83 -0
  147. package/dist/Project.d.ts +57 -0
  148. package/dist/ProjectMembership.d.ts +83 -0
  149. package/dist/Provenance.d.ts +299 -0
  150. package/dist/Quantity.d.ts +59 -0
  151. package/dist/Questionnaire.d.ts +703 -0
  152. package/dist/QuestionnaireResponse.d.ts +365 -0
  153. package/dist/Range.d.ts +40 -0
  154. package/dist/Ratio.d.ts +40 -0
  155. package/dist/Reference.d.ts +80 -0
  156. package/dist/RelatedArtifact.d.ts +72 -0
  157. package/dist/RelatedPerson.d.ts +223 -0
  158. package/dist/RequestGroup.d.ts +509 -0
  159. package/dist/ResearchDefinition.d.ts +341 -0
  160. package/dist/ResearchElementDefinition.d.ts +505 -0
  161. package/dist/ResearchStudy.d.ts +370 -0
  162. package/dist/ResearchSubject.d.ts +142 -0
  163. package/dist/Resource.d.ts +316 -0
  164. package/dist/RiskAssessment.d.ts +291 -0
  165. package/dist/RiskEvidenceSynthesis.d.ts +616 -0
  166. package/dist/SampledData.d.ts +77 -0
  167. package/dist/Schedule.d.ts +152 -0
  168. package/dist/SearchParameter.d.ts +324 -0
  169. package/dist/ServiceRequest.d.ts +362 -0
  170. package/dist/Signature.d.ts +86 -0
  171. package/dist/Slot.d.ts +160 -0
  172. package/dist/Specimen.d.ts +427 -0
  173. package/dist/SpecimenDefinition.d.ts +423 -0
  174. package/dist/StructureDefinition.d.ts +504 -0
  175. package/dist/StructureMap.d.ts +1064 -0
  176. package/dist/Subscription.d.ts +202 -0
  177. package/dist/Substance.d.ts +249 -0
  178. package/dist/SubstanceAmount.d.ts +135 -0
  179. package/dist/SubstanceNucleicAcid.d.ts +356 -0
  180. package/dist/SubstancePolymer.d.ts +470 -0
  181. package/dist/SubstanceProtein.d.ts +249 -0
  182. package/dist/SubstanceReferenceInformation.d.ts +386 -0
  183. package/dist/SubstanceSourceMaterial.d.ts +596 -0
  184. package/dist/SubstanceSpecification.d.ts +965 -0
  185. package/dist/SupplyDelivery.d.ts +240 -0
  186. package/dist/SupplyRequest.d.ts +279 -0
  187. package/dist/Task.d.ts +970 -0
  188. package/dist/TerminologyCapabilities.d.ts +820 -0
  189. package/dist/TestReport.d.ts +631 -0
  190. package/dist/TestScript.d.ts +1364 -0
  191. package/dist/Timing.d.ts +210 -0
  192. package/dist/TriggerDefinition.d.ts +81 -0
  193. package/dist/UsageContext.d.ts +74 -0
  194. package/dist/User.d.ts +59 -0
  195. package/dist/ValueSet.d.ts +830 -0
  196. package/dist/VerificationResult.d.ts +399 -0
  197. package/dist/VisionPrescription.d.ts +311 -0
  198. package/dist/index.d.ts +201 -0
  199. package/package.json +36 -0
@@ -0,0 +1,728 @@
1
+ /*
2
+ * Generated by @medplum/generator
3
+ * Do not edit manually.
4
+ */
5
+
6
+ import { CodeableConcept } from './CodeableConcept';
7
+ import { ContactDetail } from './ContactDetail';
8
+ import { Extension } from './Extension';
9
+ import { Identifier } from './Identifier';
10
+ import { Meta } from './Meta';
11
+ import { Narrative } from './Narrative';
12
+ import { Resource } from './Resource';
13
+ import { UsageContext } from './UsageContext';
14
+
15
+ /**
16
+ * Example of workflow instance.
17
+ */
18
+ export interface ExampleScenario {
19
+
20
+ /**
21
+ * This is a ExampleScenario resource
22
+ */
23
+ readonly resourceType: 'ExampleScenario';
24
+
25
+ /**
26
+ * The logical id of the resource, as used in the URL for the resource.
27
+ * Once assigned, this value never changes.
28
+ */
29
+ readonly id?: string;
30
+
31
+ /**
32
+ * The metadata about the resource. This is content that is maintained by
33
+ * the infrastructure. Changes to the content might not always be
34
+ * associated with version changes to the resource.
35
+ */
36
+ readonly meta?: Meta;
37
+
38
+ /**
39
+ * A reference to a set of rules that were followed when the resource was
40
+ * constructed, and which must be understood when processing the content.
41
+ * Often, this is a reference to an implementation guide that defines the
42
+ * special rules along with other profiles etc.
43
+ */
44
+ readonly implicitRules?: string;
45
+
46
+ /**
47
+ * The base language in which the resource is written.
48
+ */
49
+ readonly language?: string;
50
+
51
+ /**
52
+ * A human-readable narrative that contains a summary of the resource and
53
+ * can be used to represent the content of the resource to a human. The
54
+ * narrative need not encode all the structured data, but is required to
55
+ * contain sufficient detail to make it "clinically safe" for a human to
56
+ * just read the narrative. Resource definitions may define what content
57
+ * should be represented in the narrative to ensure clinical safety.
58
+ */
59
+ readonly text?: Narrative;
60
+
61
+ /**
62
+ * These resources do not have an independent existence apart from the
63
+ * resource that contains them - they cannot be identified independently,
64
+ * and nor can they have their own independent transaction scope.
65
+ */
66
+ readonly contained?: Resource[];
67
+
68
+ /**
69
+ * May be used to represent additional information that is not part of
70
+ * the basic definition of the resource. To make the use of extensions
71
+ * safe and manageable, there is a strict set of governance applied to
72
+ * the definition and use of extensions. Though any implementer can
73
+ * define an extension, there is a set of requirements that SHALL be met
74
+ * as part of the definition of the extension.
75
+ */
76
+ readonly extension?: Extension[];
77
+
78
+ /**
79
+ * May be used to represent additional information that is not part of
80
+ * the basic definition of the resource and that modifies the
81
+ * understanding of the element that contains it and/or the understanding
82
+ * of the containing element's descendants. Usually modifier elements
83
+ * provide negation or qualification. To make the use of extensions safe
84
+ * and manageable, there is a strict set of governance applied to the
85
+ * definition and use of extensions. Though any implementer is allowed to
86
+ * define an extension, there is a set of requirements that SHALL be met
87
+ * as part of the definition of the extension. Applications processing a
88
+ * resource are required to check for modifier extensions.
89
+ *
90
+ * Modifier extensions SHALL NOT change the meaning of any elements on
91
+ * Resource or DomainResource (including cannot change the meaning of
92
+ * modifierExtension itself).
93
+ */
94
+ readonly modifierExtension?: Extension[];
95
+
96
+ /**
97
+ * An absolute URI that is used to identify this example scenario when it
98
+ * is referenced in a specification, model, design or an instance; also
99
+ * called its canonical identifier. This SHOULD be globally unique and
100
+ * SHOULD be a literal address at which at which an authoritative
101
+ * instance of this example scenario is (or will be) published. This URL
102
+ * can be the target of a canonical reference. It SHALL remain the same
103
+ * when the example scenario is stored on different servers.
104
+ */
105
+ readonly url?: string;
106
+
107
+ /**
108
+ * A formal identifier that is used to identify this example scenario
109
+ * when it is represented in other formats, or referenced in a
110
+ * specification, model, design or an instance.
111
+ */
112
+ readonly identifier?: Identifier[];
113
+
114
+ /**
115
+ * The identifier that is used to identify this version of the example
116
+ * scenario when it is referenced in a specification, model, design or
117
+ * instance. This is an arbitrary value managed by the example scenario
118
+ * author and is not expected to be globally unique. For example, it
119
+ * might be a timestamp (e.g. yyyymmdd) if a managed version is not
120
+ * available. There is also no expectation that versions can be placed in
121
+ * a lexicographical sequence.
122
+ */
123
+ readonly version?: string;
124
+
125
+ /**
126
+ * A natural language name identifying the example scenario. This name
127
+ * should be usable as an identifier for the module by machine processing
128
+ * applications such as code generation.
129
+ */
130
+ readonly name?: string;
131
+
132
+ /**
133
+ * The status of this example scenario. Enables tracking the life-cycle
134
+ * of the content.
135
+ */
136
+ readonly status?: string;
137
+
138
+ /**
139
+ * A Boolean value to indicate that this example scenario is authored for
140
+ * testing purposes (or education/evaluation/marketing) and is not
141
+ * intended to be used for genuine usage.
142
+ */
143
+ readonly experimental?: boolean;
144
+
145
+ /**
146
+ * The date (and optionally time) when the example scenario was
147
+ * published. The date must change when the business version changes and
148
+ * it must change if the status code changes. In addition, it should
149
+ * change when the substantive content of the example scenario changes.
150
+ * (e.g. the 'content logical definition').
151
+ */
152
+ readonly date?: string;
153
+
154
+ /**
155
+ * The name of the organization or individual that published the example
156
+ * scenario.
157
+ */
158
+ readonly publisher?: string;
159
+
160
+ /**
161
+ * Contact details to assist a user in finding and communicating with the
162
+ * publisher.
163
+ */
164
+ readonly contact?: ContactDetail[];
165
+
166
+ /**
167
+ * The content was developed with a focus and intent of supporting the
168
+ * contexts that are listed. These contexts may be general categories
169
+ * (gender, age, ...) or may be references to specific programs
170
+ * (insurance plans, studies, ...) and may be used to assist with
171
+ * indexing and searching for appropriate example scenario instances.
172
+ */
173
+ readonly useContext?: UsageContext[];
174
+
175
+ /**
176
+ * A legal or geographic region in which the example scenario is intended
177
+ * to be used.
178
+ */
179
+ readonly jurisdiction?: CodeableConcept[];
180
+
181
+ /**
182
+ * A copyright statement relating to the example scenario and/or its
183
+ * contents. Copyright statements are generally legal restrictions on the
184
+ * use and publishing of the example scenario.
185
+ */
186
+ readonly copyright?: string;
187
+
188
+ /**
189
+ * What the example scenario resource is created for. This should not be
190
+ * used to show the business purpose of the scenario itself, but the
191
+ * purpose of documenting a scenario.
192
+ */
193
+ readonly purpose?: string;
194
+
195
+ /**
196
+ * Actor participating in the resource.
197
+ */
198
+ readonly actor?: ExampleScenarioActor[];
199
+
200
+ /**
201
+ * Each resource and each version that is present in the workflow.
202
+ */
203
+ readonly instance?: ExampleScenarioInstance[];
204
+
205
+ /**
206
+ * Each major process - a group of operations.
207
+ */
208
+ readonly process?: ExampleScenarioProcess[];
209
+
210
+ /**
211
+ * Another nested workflow.
212
+ */
213
+ readonly workflow?: string[];
214
+ }
215
+
216
+ /**
217
+ * Actor participating in the resource.
218
+ */
219
+ export interface ExampleScenarioActor {
220
+
221
+ /**
222
+ * Unique id for the element within a resource (for internal references).
223
+ * This may be any string value that does not contain spaces.
224
+ */
225
+ readonly id?: string;
226
+
227
+ /**
228
+ * May be used to represent additional information that is not part of
229
+ * the basic definition of the element. To make the use of extensions
230
+ * safe and manageable, there is a strict set of governance applied to
231
+ * the definition and use of extensions. Though any implementer can
232
+ * define an extension, there is a set of requirements that SHALL be met
233
+ * as part of the definition of the extension.
234
+ */
235
+ readonly extension?: Extension[];
236
+
237
+ /**
238
+ * May be used to represent additional information that is not part of
239
+ * the basic definition of the element and that modifies the
240
+ * understanding of the element in which it is contained and/or the
241
+ * understanding of the containing element's descendants. Usually
242
+ * modifier elements provide negation or qualification. To make the use
243
+ * of extensions safe and manageable, there is a strict set of governance
244
+ * applied to the definition and use of extensions. Though any
245
+ * implementer can define an extension, there is a set of requirements
246
+ * that SHALL be met as part of the definition of the extension.
247
+ * Applications processing a resource are required to check for modifier
248
+ * extensions.
249
+ *
250
+ * Modifier extensions SHALL NOT change the meaning of any elements on
251
+ * Resource or DomainResource (including cannot change the meaning of
252
+ * modifierExtension itself).
253
+ */
254
+ readonly modifierExtension?: Extension[];
255
+
256
+ /**
257
+ * ID or acronym of actor.
258
+ */
259
+ readonly actorId?: string;
260
+
261
+ /**
262
+ * The type of actor - person or system.
263
+ */
264
+ readonly type?: string;
265
+
266
+ /**
267
+ * The name of the actor as shown in the page.
268
+ */
269
+ readonly name?: string;
270
+
271
+ /**
272
+ * The description of the actor.
273
+ */
274
+ readonly description?: string;
275
+ }
276
+
277
+ /**
278
+ * Each resource and each version that is present in the workflow.
279
+ */
280
+ export interface ExampleScenarioInstance {
281
+
282
+ /**
283
+ * Unique id for the element within a resource (for internal references).
284
+ * This may be any string value that does not contain spaces.
285
+ */
286
+ readonly id?: string;
287
+
288
+ /**
289
+ * May be used to represent additional information that is not part of
290
+ * the basic definition of the element. To make the use of extensions
291
+ * safe and manageable, there is a strict set of governance applied to
292
+ * the definition and use of extensions. Though any implementer can
293
+ * define an extension, there is a set of requirements that SHALL be met
294
+ * as part of the definition of the extension.
295
+ */
296
+ readonly extension?: Extension[];
297
+
298
+ /**
299
+ * May be used to represent additional information that is not part of
300
+ * the basic definition of the element and that modifies the
301
+ * understanding of the element in which it is contained and/or the
302
+ * understanding of the containing element's descendants. Usually
303
+ * modifier elements provide negation or qualification. To make the use
304
+ * of extensions safe and manageable, there is a strict set of governance
305
+ * applied to the definition and use of extensions. Though any
306
+ * implementer can define an extension, there is a set of requirements
307
+ * that SHALL be met as part of the definition of the extension.
308
+ * Applications processing a resource are required to check for modifier
309
+ * extensions.
310
+ *
311
+ * Modifier extensions SHALL NOT change the meaning of any elements on
312
+ * Resource or DomainResource (including cannot change the meaning of
313
+ * modifierExtension itself).
314
+ */
315
+ readonly modifierExtension?: Extension[];
316
+
317
+ /**
318
+ * The id of the resource for referencing.
319
+ */
320
+ readonly resourceId?: string;
321
+
322
+ /**
323
+ * The type of the resource.
324
+ */
325
+ readonly resourceType?: string;
326
+
327
+ /**
328
+ * A short name for the resource instance.
329
+ */
330
+ readonly name?: string;
331
+
332
+ /**
333
+ * Human-friendly description of the resource instance.
334
+ */
335
+ readonly description?: string;
336
+
337
+ /**
338
+ * A specific version of the resource.
339
+ */
340
+ readonly version?: ExampleScenarioInstanceVersion[];
341
+
342
+ /**
343
+ * Resources contained in the instance (e.g. the observations contained
344
+ * in a bundle).
345
+ */
346
+ readonly containedInstance?: ExampleScenarioInstanceContainedInstance[];
347
+ }
348
+
349
+ /**
350
+ * Resources contained in the instance (e.g. the observations contained
351
+ * in a bundle).
352
+ */
353
+ export interface ExampleScenarioInstanceContainedInstance {
354
+
355
+ /**
356
+ * Unique id for the element within a resource (for internal references).
357
+ * This may be any string value that does not contain spaces.
358
+ */
359
+ readonly id?: string;
360
+
361
+ /**
362
+ * May be used to represent additional information that is not part of
363
+ * the basic definition of the element. To make the use of extensions
364
+ * safe and manageable, there is a strict set of governance applied to
365
+ * the definition and use of extensions. Though any implementer can
366
+ * define an extension, there is a set of requirements that SHALL be met
367
+ * as part of the definition of the extension.
368
+ */
369
+ readonly extension?: Extension[];
370
+
371
+ /**
372
+ * May be used to represent additional information that is not part of
373
+ * the basic definition of the element and that modifies the
374
+ * understanding of the element in which it is contained and/or the
375
+ * understanding of the containing element's descendants. Usually
376
+ * modifier elements provide negation or qualification. To make the use
377
+ * of extensions safe and manageable, there is a strict set of governance
378
+ * applied to the definition and use of extensions. Though any
379
+ * implementer can define an extension, there is a set of requirements
380
+ * that SHALL be met as part of the definition of the extension.
381
+ * Applications processing a resource are required to check for modifier
382
+ * extensions.
383
+ *
384
+ * Modifier extensions SHALL NOT change the meaning of any elements on
385
+ * Resource or DomainResource (including cannot change the meaning of
386
+ * modifierExtension itself).
387
+ */
388
+ readonly modifierExtension?: Extension[];
389
+
390
+ /**
391
+ * Each resource contained in the instance.
392
+ */
393
+ readonly resourceId?: string;
394
+
395
+ /**
396
+ * A specific version of a resource contained in the instance.
397
+ */
398
+ readonly versionId?: string;
399
+ }
400
+
401
+ /**
402
+ * A specific version of the resource.
403
+ */
404
+ export interface ExampleScenarioInstanceVersion {
405
+
406
+ /**
407
+ * Unique id for the element within a resource (for internal references).
408
+ * This may be any string value that does not contain spaces.
409
+ */
410
+ readonly id?: string;
411
+
412
+ /**
413
+ * May be used to represent additional information that is not part of
414
+ * the basic definition of the element. To make the use of extensions
415
+ * safe and manageable, there is a strict set of governance applied to
416
+ * the definition and use of extensions. Though any implementer can
417
+ * define an extension, there is a set of requirements that SHALL be met
418
+ * as part of the definition of the extension.
419
+ */
420
+ readonly extension?: Extension[];
421
+
422
+ /**
423
+ * May be used to represent additional information that is not part of
424
+ * the basic definition of the element and that modifies the
425
+ * understanding of the element in which it is contained and/or the
426
+ * understanding of the containing element's descendants. Usually
427
+ * modifier elements provide negation or qualification. To make the use
428
+ * of extensions safe and manageable, there is a strict set of governance
429
+ * applied to the definition and use of extensions. Though any
430
+ * implementer can define an extension, there is a set of requirements
431
+ * that SHALL be met as part of the definition of the extension.
432
+ * Applications processing a resource are required to check for modifier
433
+ * extensions.
434
+ *
435
+ * Modifier extensions SHALL NOT change the meaning of any elements on
436
+ * Resource or DomainResource (including cannot change the meaning of
437
+ * modifierExtension itself).
438
+ */
439
+ readonly modifierExtension?: Extension[];
440
+
441
+ /**
442
+ * The identifier of a specific version of a resource.
443
+ */
444
+ readonly versionId?: string;
445
+
446
+ /**
447
+ * The description of the resource version.
448
+ */
449
+ readonly description?: string;
450
+ }
451
+
452
+ /**
453
+ * Each major process - a group of operations.
454
+ */
455
+ export interface ExampleScenarioProcess {
456
+
457
+ /**
458
+ * Unique id for the element within a resource (for internal references).
459
+ * This may be any string value that does not contain spaces.
460
+ */
461
+ readonly id?: string;
462
+
463
+ /**
464
+ * May be used to represent additional information that is not part of
465
+ * the basic definition of the element. To make the use of extensions
466
+ * safe and manageable, there is a strict set of governance applied to
467
+ * the definition and use of extensions. Though any implementer can
468
+ * define an extension, there is a set of requirements that SHALL be met
469
+ * as part of the definition of the extension.
470
+ */
471
+ readonly extension?: Extension[];
472
+
473
+ /**
474
+ * May be used to represent additional information that is not part of
475
+ * the basic definition of the element and that modifies the
476
+ * understanding of the element in which it is contained and/or the
477
+ * understanding of the containing element's descendants. Usually
478
+ * modifier elements provide negation or qualification. To make the use
479
+ * of extensions safe and manageable, there is a strict set of governance
480
+ * applied to the definition and use of extensions. Though any
481
+ * implementer can define an extension, there is a set of requirements
482
+ * that SHALL be met as part of the definition of the extension.
483
+ * Applications processing a resource are required to check for modifier
484
+ * extensions.
485
+ *
486
+ * Modifier extensions SHALL NOT change the meaning of any elements on
487
+ * Resource or DomainResource (including cannot change the meaning of
488
+ * modifierExtension itself).
489
+ */
490
+ readonly modifierExtension?: Extension[];
491
+
492
+ /**
493
+ * The diagram title of the group of operations.
494
+ */
495
+ readonly title?: string;
496
+
497
+ /**
498
+ * A longer description of the group of operations.
499
+ */
500
+ readonly description?: string;
501
+
502
+ /**
503
+ * Description of initial status before the process starts.
504
+ */
505
+ readonly preConditions?: string;
506
+
507
+ /**
508
+ * Description of final status after the process ends.
509
+ */
510
+ readonly postConditions?: string;
511
+
512
+ /**
513
+ * Each step of the process.
514
+ */
515
+ readonly step?: ExampleScenarioProcessStep[];
516
+ }
517
+
518
+ /**
519
+ * Each step of the process.
520
+ */
521
+ export interface ExampleScenarioProcessStep {
522
+
523
+ /**
524
+ * Unique id for the element within a resource (for internal references).
525
+ * This may be any string value that does not contain spaces.
526
+ */
527
+ readonly id?: string;
528
+
529
+ /**
530
+ * May be used to represent additional information that is not part of
531
+ * the basic definition of the element. To make the use of extensions
532
+ * safe and manageable, there is a strict set of governance applied to
533
+ * the definition and use of extensions. Though any implementer can
534
+ * define an extension, there is a set of requirements that SHALL be met
535
+ * as part of the definition of the extension.
536
+ */
537
+ readonly extension?: Extension[];
538
+
539
+ /**
540
+ * May be used to represent additional information that is not part of
541
+ * the basic definition of the element and that modifies the
542
+ * understanding of the element in which it is contained and/or the
543
+ * understanding of the containing element's descendants. Usually
544
+ * modifier elements provide negation or qualification. To make the use
545
+ * of extensions safe and manageable, there is a strict set of governance
546
+ * applied to the definition and use of extensions. Though any
547
+ * implementer can define an extension, there is a set of requirements
548
+ * that SHALL be met as part of the definition of the extension.
549
+ * Applications processing a resource are required to check for modifier
550
+ * extensions.
551
+ *
552
+ * Modifier extensions SHALL NOT change the meaning of any elements on
553
+ * Resource or DomainResource (including cannot change the meaning of
554
+ * modifierExtension itself).
555
+ */
556
+ readonly modifierExtension?: Extension[];
557
+
558
+ /**
559
+ * Nested process.
560
+ */
561
+ readonly process?: ExampleScenarioProcess[];
562
+
563
+ /**
564
+ * If there is a pause in the flow.
565
+ */
566
+ readonly pause?: boolean;
567
+
568
+ /**
569
+ * Each interaction or action.
570
+ */
571
+ readonly operation?: ExampleScenarioProcessStepOperation;
572
+
573
+ /**
574
+ * Indicates an alternative step that can be taken instead of the
575
+ * operations on the base step in exceptional/atypical circumstances.
576
+ */
577
+ readonly alternative?: ExampleScenarioProcessStepAlternative[];
578
+ }
579
+
580
+ /**
581
+ * Indicates an alternative step that can be taken instead of the
582
+ * operations on the base step in exceptional/atypical circumstances.
583
+ */
584
+ export interface ExampleScenarioProcessStepAlternative {
585
+
586
+ /**
587
+ * Unique id for the element within a resource (for internal references).
588
+ * This may be any string value that does not contain spaces.
589
+ */
590
+ readonly id?: string;
591
+
592
+ /**
593
+ * May be used to represent additional information that is not part of
594
+ * the basic definition of the element. To make the use of extensions
595
+ * safe and manageable, there is a strict set of governance applied to
596
+ * the definition and use of extensions. Though any implementer can
597
+ * define an extension, there is a set of requirements that SHALL be met
598
+ * as part of the definition of the extension.
599
+ */
600
+ readonly extension?: Extension[];
601
+
602
+ /**
603
+ * May be used to represent additional information that is not part of
604
+ * the basic definition of the element and that modifies the
605
+ * understanding of the element in which it is contained and/or the
606
+ * understanding of the containing element's descendants. Usually
607
+ * modifier elements provide negation or qualification. To make the use
608
+ * of extensions safe and manageable, there is a strict set of governance
609
+ * applied to the definition and use of extensions. Though any
610
+ * implementer can define an extension, there is a set of requirements
611
+ * that SHALL be met as part of the definition of the extension.
612
+ * Applications processing a resource are required to check for modifier
613
+ * extensions.
614
+ *
615
+ * Modifier extensions SHALL NOT change the meaning of any elements on
616
+ * Resource or DomainResource (including cannot change the meaning of
617
+ * modifierExtension itself).
618
+ */
619
+ readonly modifierExtension?: Extension[];
620
+
621
+ /**
622
+ * The label to display for the alternative that gives a sense of the
623
+ * circumstance in which the alternative should be invoked.
624
+ */
625
+ readonly title?: string;
626
+
627
+ /**
628
+ * A human-readable description of the alternative explaining when the
629
+ * alternative should occur rather than the base step.
630
+ */
631
+ readonly description?: string;
632
+
633
+ /**
634
+ * What happens in each alternative option.
635
+ */
636
+ readonly step?: ExampleScenarioProcessStep[];
637
+ }
638
+
639
+ /**
640
+ * Each interaction or action.
641
+ */
642
+ export interface ExampleScenarioProcessStepOperation {
643
+
644
+ /**
645
+ * Unique id for the element within a resource (for internal references).
646
+ * This may be any string value that does not contain spaces.
647
+ */
648
+ readonly id?: string;
649
+
650
+ /**
651
+ * May be used to represent additional information that is not part of
652
+ * the basic definition of the element. To make the use of extensions
653
+ * safe and manageable, there is a strict set of governance applied to
654
+ * the definition and use of extensions. Though any implementer can
655
+ * define an extension, there is a set of requirements that SHALL be met
656
+ * as part of the definition of the extension.
657
+ */
658
+ readonly extension?: Extension[];
659
+
660
+ /**
661
+ * May be used to represent additional information that is not part of
662
+ * the basic definition of the element and that modifies the
663
+ * understanding of the element in which it is contained and/or the
664
+ * understanding of the containing element's descendants. Usually
665
+ * modifier elements provide negation or qualification. To make the use
666
+ * of extensions safe and manageable, there is a strict set of governance
667
+ * applied to the definition and use of extensions. Though any
668
+ * implementer can define an extension, there is a set of requirements
669
+ * that SHALL be met as part of the definition of the extension.
670
+ * Applications processing a resource are required to check for modifier
671
+ * extensions.
672
+ *
673
+ * Modifier extensions SHALL NOT change the meaning of any elements on
674
+ * Resource or DomainResource (including cannot change the meaning of
675
+ * modifierExtension itself).
676
+ */
677
+ readonly modifierExtension?: Extension[];
678
+
679
+ /**
680
+ * The sequential number of the interaction, e.g. 1.2.5.
681
+ */
682
+ readonly number?: string;
683
+
684
+ /**
685
+ * The type of operation - CRUD.
686
+ */
687
+ readonly type?: string;
688
+
689
+ /**
690
+ * The human-friendly name of the interaction.
691
+ */
692
+ readonly name?: string;
693
+
694
+ /**
695
+ * Who starts the transaction.
696
+ */
697
+ readonly initiator?: string;
698
+
699
+ /**
700
+ * Who receives the transaction.
701
+ */
702
+ readonly receiver?: string;
703
+
704
+ /**
705
+ * A comment to be inserted in the diagram.
706
+ */
707
+ readonly description?: string;
708
+
709
+ /**
710
+ * Whether the initiator is deactivated right after the transaction.
711
+ */
712
+ readonly initiatorActive?: boolean;
713
+
714
+ /**
715
+ * Whether the receiver is deactivated right after the transaction.
716
+ */
717
+ readonly receiverActive?: boolean;
718
+
719
+ /**
720
+ * Each resource instance used by the initiator.
721
+ */
722
+ readonly request?: ExampleScenarioInstanceContainedInstance;
723
+
724
+ /**
725
+ * Each resource instance used by the responder.
726
+ */
727
+ readonly response?: ExampleScenarioInstanceContainedInstance;
728
+ }