@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,820 @@
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 { Meta } from './Meta';
10
+ import { Narrative } from './Narrative';
11
+ import { Resource } from './Resource';
12
+ import { UsageContext } from './UsageContext';
13
+
14
+ /**
15
+ * A TerminologyCapabilities resource documents a set of capabilities
16
+ * (behaviors) of a FHIR Terminology Server that may be used as a
17
+ * statement of actual server functionality or a statement of required or
18
+ * desired server implementation.
19
+ */
20
+ export interface TerminologyCapabilities {
21
+
22
+ /**
23
+ * This is a TerminologyCapabilities resource
24
+ */
25
+ readonly resourceType: 'TerminologyCapabilities';
26
+
27
+ /**
28
+ * The logical id of the resource, as used in the URL for the resource.
29
+ * Once assigned, this value never changes.
30
+ */
31
+ readonly id?: string;
32
+
33
+ /**
34
+ * The metadata about the resource. This is content that is maintained by
35
+ * the infrastructure. Changes to the content might not always be
36
+ * associated with version changes to the resource.
37
+ */
38
+ readonly meta?: Meta;
39
+
40
+ /**
41
+ * A reference to a set of rules that were followed when the resource was
42
+ * constructed, and which must be understood when processing the content.
43
+ * Often, this is a reference to an implementation guide that defines the
44
+ * special rules along with other profiles etc.
45
+ */
46
+ readonly implicitRules?: string;
47
+
48
+ /**
49
+ * The base language in which the resource is written.
50
+ */
51
+ readonly language?: string;
52
+
53
+ /**
54
+ * A human-readable narrative that contains a summary of the resource and
55
+ * can be used to represent the content of the resource to a human. The
56
+ * narrative need not encode all the structured data, but is required to
57
+ * contain sufficient detail to make it "clinically safe" for a human to
58
+ * just read the narrative. Resource definitions may define what content
59
+ * should be represented in the narrative to ensure clinical safety.
60
+ */
61
+ readonly text?: Narrative;
62
+
63
+ /**
64
+ * These resources do not have an independent existence apart from the
65
+ * resource that contains them - they cannot be identified independently,
66
+ * and nor can they have their own independent transaction scope.
67
+ */
68
+ readonly contained?: Resource[];
69
+
70
+ /**
71
+ * May be used to represent additional information that is not part of
72
+ * the basic definition of the resource. To make the use of extensions
73
+ * safe and manageable, there is a strict set of governance applied to
74
+ * the definition and use of extensions. Though any implementer can
75
+ * define an extension, there is a set of requirements that SHALL be met
76
+ * as part of the definition of the extension.
77
+ */
78
+ readonly extension?: Extension[];
79
+
80
+ /**
81
+ * May be used to represent additional information that is not part of
82
+ * the basic definition of the resource and that modifies the
83
+ * understanding of the element that contains it and/or the understanding
84
+ * of the containing element's descendants. Usually modifier elements
85
+ * provide negation or qualification. To make the use of extensions safe
86
+ * and manageable, there is a strict set of governance applied to the
87
+ * definition and use of extensions. Though any implementer is allowed to
88
+ * define an extension, there is a set of requirements that SHALL be met
89
+ * as part of the definition of the extension. Applications processing a
90
+ * resource are required to check for modifier extensions.
91
+ *
92
+ * Modifier extensions SHALL NOT change the meaning of any elements on
93
+ * Resource or DomainResource (including cannot change the meaning of
94
+ * modifierExtension itself).
95
+ */
96
+ readonly modifierExtension?: Extension[];
97
+
98
+ /**
99
+ * An absolute URI that is used to identify this terminology capabilities
100
+ * when it is referenced in a specification, model, design or an
101
+ * instance; also called its canonical identifier. This SHOULD be
102
+ * globally unique and SHOULD be a literal address at which at which an
103
+ * authoritative instance of this terminology capabilities is (or will
104
+ * be) published. This URL can be the target of a canonical reference. It
105
+ * SHALL remain the same when the terminology capabilities is stored on
106
+ * different servers.
107
+ */
108
+ readonly url?: string;
109
+
110
+ /**
111
+ * The identifier that is used to identify this version of the
112
+ * terminology capabilities when it is referenced in a specification,
113
+ * model, design or instance. This is an arbitrary value managed by the
114
+ * terminology capabilities author and is not expected to be globally
115
+ * unique. For example, it might be a timestamp (e.g. yyyymmdd) if a
116
+ * managed version is not available. There is also no expectation that
117
+ * versions can be placed in a lexicographical sequence.
118
+ */
119
+ readonly version?: string;
120
+
121
+ /**
122
+ * A natural language name identifying the terminology capabilities. This
123
+ * name should be usable as an identifier for the module by machine
124
+ * processing applications such as code generation.
125
+ */
126
+ readonly name?: string;
127
+
128
+ /**
129
+ * A short, descriptive, user-friendly title for the terminology
130
+ * capabilities.
131
+ */
132
+ readonly title?: string;
133
+
134
+ /**
135
+ * The status of this terminology capabilities. Enables tracking the
136
+ * life-cycle of the content.
137
+ */
138
+ readonly status?: string;
139
+
140
+ /**
141
+ * A Boolean value to indicate that this terminology capabilities is
142
+ * authored for testing purposes (or education/evaluation/marketing) and
143
+ * is not intended to be used for genuine usage.
144
+ */
145
+ readonly experimental?: boolean;
146
+
147
+ /**
148
+ * The date (and optionally time) when the terminology capabilities was
149
+ * published. The date must change when the business version changes and
150
+ * it must change if the status code changes. In addition, it should
151
+ * change when the substantive content of the terminology capabilities
152
+ * changes.
153
+ */
154
+ readonly date?: string;
155
+
156
+ /**
157
+ * The name of the organization or individual that published the
158
+ * terminology capabilities.
159
+ */
160
+ readonly publisher?: string;
161
+
162
+ /**
163
+ * Contact details to assist a user in finding and communicating with the
164
+ * publisher.
165
+ */
166
+ readonly contact?: ContactDetail[];
167
+
168
+ /**
169
+ * A free text natural language description of the terminology
170
+ * capabilities from a consumer's perspective. Typically, this is used
171
+ * when the capability statement describes a desired rather than an
172
+ * actual solution, for example as a formal expression of requirements as
173
+ * part of an RFP.
174
+ */
175
+ readonly description?: string;
176
+
177
+ /**
178
+ * The content was developed with a focus and intent of supporting the
179
+ * contexts that are listed. These contexts may be general categories
180
+ * (gender, age, ...) or may be references to specific programs
181
+ * (insurance plans, studies, ...) and may be used to assist with
182
+ * indexing and searching for appropriate terminology capabilities
183
+ * instances.
184
+ */
185
+ readonly useContext?: UsageContext[];
186
+
187
+ /**
188
+ * A legal or geographic region in which the terminology capabilities is
189
+ * intended to be used.
190
+ */
191
+ readonly jurisdiction?: CodeableConcept[];
192
+
193
+ /**
194
+ * Explanation of why this terminology capabilities is needed and why it
195
+ * has been designed as it has.
196
+ */
197
+ readonly purpose?: string;
198
+
199
+ /**
200
+ * A copyright statement relating to the terminology capabilities and/or
201
+ * its contents. Copyright statements are generally legal restrictions on
202
+ * the use and publishing of the terminology capabilities.
203
+ */
204
+ readonly copyright?: string;
205
+
206
+ /**
207
+ * The way that this statement is intended to be used, to describe an
208
+ * actual running instance of software, a particular product (kind, not
209
+ * instance of software) or a class of implementation (e.g. a desired
210
+ * purchase).
211
+ */
212
+ readonly kind?: string;
213
+
214
+ /**
215
+ * Software that is covered by this terminology capability statement. It
216
+ * is used when the statement describes the capabilities of a particular
217
+ * software version, independent of an installation.
218
+ */
219
+ readonly software?: TerminologyCapabilitiesSoftware;
220
+
221
+ /**
222
+ * Identifies a specific implementation instance that is described by the
223
+ * terminology capability statement - i.e. a particular installation,
224
+ * rather than the capabilities of a software program.
225
+ */
226
+ readonly implementation?: TerminologyCapabilitiesImplementation;
227
+
228
+ /**
229
+ * Whether the server supports lockedDate.
230
+ */
231
+ readonly lockedDate?: boolean;
232
+
233
+ /**
234
+ * Identifies a code system that is supported by the server. If there is
235
+ * a no code system URL, then this declares the general assumptions a
236
+ * client can make about support for any CodeSystem resource.
237
+ */
238
+ readonly codeSystem?: TerminologyCapabilitiesCodeSystem[];
239
+
240
+ /**
241
+ * Information about the
242
+ * [ValueSet/$expand](valueset-operation-expand.html) operation.
243
+ */
244
+ readonly expansion?: TerminologyCapabilitiesExpansion;
245
+
246
+ /**
247
+ * The degree to which the server supports the code search parameter on
248
+ * ValueSet, if it is supported.
249
+ */
250
+ readonly codeSearch?: string;
251
+
252
+ /**
253
+ * Information about the
254
+ * [ValueSet/$validate-code](valueset-operation-validate-code.html)
255
+ * operation.
256
+ */
257
+ readonly validateCode?: TerminologyCapabilitiesValidateCode;
258
+
259
+ /**
260
+ * Information about the
261
+ * [ConceptMap/$translate](conceptmap-operation-translate.html)
262
+ * operation.
263
+ */
264
+ readonly translation?: TerminologyCapabilitiesTranslation;
265
+
266
+ /**
267
+ * Whether the $closure operation is supported.
268
+ */
269
+ readonly closure?: TerminologyCapabilitiesClosure;
270
+ }
271
+
272
+ /**
273
+ * Whether the $closure operation is supported.
274
+ */
275
+ export interface TerminologyCapabilitiesClosure {
276
+
277
+ /**
278
+ * Unique id for the element within a resource (for internal references).
279
+ * This may be any string value that does not contain spaces.
280
+ */
281
+ readonly id?: string;
282
+
283
+ /**
284
+ * May be used to represent additional information that is not part of
285
+ * the basic definition of the element. To make the use of extensions
286
+ * safe and manageable, there is a strict set of governance applied to
287
+ * the definition and use of extensions. Though any implementer can
288
+ * define an extension, there is a set of requirements that SHALL be met
289
+ * as part of the definition of the extension.
290
+ */
291
+ readonly extension?: Extension[];
292
+
293
+ /**
294
+ * May be used to represent additional information that is not part of
295
+ * the basic definition of the element and that modifies the
296
+ * understanding of the element in which it is contained and/or the
297
+ * understanding of the containing element's descendants. Usually
298
+ * modifier elements provide negation or qualification. To make the use
299
+ * of extensions safe and manageable, there is a strict set of governance
300
+ * applied to the definition and use of extensions. Though any
301
+ * implementer can define an extension, there is a set of requirements
302
+ * that SHALL be met as part of the definition of the extension.
303
+ * Applications processing a resource are required to check for modifier
304
+ * extensions.
305
+ *
306
+ * Modifier extensions SHALL NOT change the meaning of any elements on
307
+ * Resource or DomainResource (including cannot change the meaning of
308
+ * modifierExtension itself).
309
+ */
310
+ readonly modifierExtension?: Extension[];
311
+
312
+ /**
313
+ * If cross-system closure is supported.
314
+ */
315
+ readonly translation?: boolean;
316
+ }
317
+
318
+ /**
319
+ * Identifies a code system that is supported by the server. If there is
320
+ * a no code system URL, then this declares the general assumptions a
321
+ * client can make about support for any CodeSystem resource.
322
+ */
323
+ export interface TerminologyCapabilitiesCodeSystem {
324
+
325
+ /**
326
+ * Unique id for the element within a resource (for internal references).
327
+ * This may be any string value that does not contain spaces.
328
+ */
329
+ readonly id?: string;
330
+
331
+ /**
332
+ * May be used to represent additional information that is not part of
333
+ * the basic definition of the element. To make the use of extensions
334
+ * safe and manageable, there is a strict set of governance applied to
335
+ * the definition and use of extensions. Though any implementer can
336
+ * define an extension, there is a set of requirements that SHALL be met
337
+ * as part of the definition of the extension.
338
+ */
339
+ readonly extension?: Extension[];
340
+
341
+ /**
342
+ * May be used to represent additional information that is not part of
343
+ * the basic definition of the element and that modifies the
344
+ * understanding of the element in which it is contained and/or the
345
+ * understanding of the containing element's descendants. Usually
346
+ * modifier elements provide negation or qualification. To make the use
347
+ * of extensions safe and manageable, there is a strict set of governance
348
+ * applied to the definition and use of extensions. Though any
349
+ * implementer can define an extension, there is a set of requirements
350
+ * that SHALL be met as part of the definition of the extension.
351
+ * Applications processing a resource are required to check for modifier
352
+ * extensions.
353
+ *
354
+ * Modifier extensions SHALL NOT change the meaning of any elements on
355
+ * Resource or DomainResource (including cannot change the meaning of
356
+ * modifierExtension itself).
357
+ */
358
+ readonly modifierExtension?: Extension[];
359
+
360
+ /**
361
+ * URI for the Code System.
362
+ */
363
+ readonly uri?: string;
364
+
365
+ /**
366
+ * For the code system, a list of versions that are supported by the
367
+ * server.
368
+ */
369
+ readonly version?: TerminologyCapabilitiesCodeSystemVersion[];
370
+
371
+ /**
372
+ * True if subsumption is supported for this version of the code system.
373
+ */
374
+ readonly subsumption?: boolean;
375
+ }
376
+
377
+ /**
378
+ * For the code system, a list of versions that are supported by the
379
+ * server.
380
+ */
381
+ export interface TerminologyCapabilitiesCodeSystemVersion {
382
+
383
+ /**
384
+ * Unique id for the element within a resource (for internal references).
385
+ * This may be any string value that does not contain spaces.
386
+ */
387
+ readonly id?: string;
388
+
389
+ /**
390
+ * May be used to represent additional information that is not part of
391
+ * the basic definition of the element. To make the use of extensions
392
+ * safe and manageable, there is a strict set of governance applied to
393
+ * the definition and use of extensions. Though any implementer can
394
+ * define an extension, there is a set of requirements that SHALL be met
395
+ * as part of the definition of the extension.
396
+ */
397
+ readonly extension?: Extension[];
398
+
399
+ /**
400
+ * May be used to represent additional information that is not part of
401
+ * the basic definition of the element and that modifies the
402
+ * understanding of the element in which it is contained and/or the
403
+ * understanding of the containing element's descendants. Usually
404
+ * modifier elements provide negation or qualification. To make the use
405
+ * of extensions safe and manageable, there is a strict set of governance
406
+ * applied to the definition and use of extensions. Though any
407
+ * implementer can define an extension, there is a set of requirements
408
+ * that SHALL be met as part of the definition of the extension.
409
+ * Applications processing a resource are required to check for modifier
410
+ * extensions.
411
+ *
412
+ * Modifier extensions SHALL NOT change the meaning of any elements on
413
+ * Resource or DomainResource (including cannot change the meaning of
414
+ * modifierExtension itself).
415
+ */
416
+ readonly modifierExtension?: Extension[];
417
+
418
+ /**
419
+ * For version-less code systems, there should be a single version with
420
+ * no identifier.
421
+ */
422
+ readonly code?: string;
423
+
424
+ /**
425
+ * If this is the default version for this code system.
426
+ */
427
+ readonly isDefault?: boolean;
428
+
429
+ /**
430
+ * If the compositional grammar defined by the code system is supported.
431
+ */
432
+ readonly compositional?: boolean;
433
+
434
+ /**
435
+ * Language Displays supported.
436
+ */
437
+ readonly language?: string[];
438
+
439
+ /**
440
+ * Filter Properties supported.
441
+ */
442
+ readonly filter?: TerminologyCapabilitiesCodeSystemVersionFilter[];
443
+
444
+ /**
445
+ * Properties supported for $lookup.
446
+ */
447
+ readonly property?: string[];
448
+ }
449
+
450
+ /**
451
+ * Filter Properties supported.
452
+ */
453
+ export interface TerminologyCapabilitiesCodeSystemVersionFilter {
454
+
455
+ /**
456
+ * Unique id for the element within a resource (for internal references).
457
+ * This may be any string value that does not contain spaces.
458
+ */
459
+ readonly id?: string;
460
+
461
+ /**
462
+ * May be used to represent additional information that is not part of
463
+ * the basic definition of the element. To make the use of extensions
464
+ * safe and manageable, there is a strict set of governance applied to
465
+ * the definition and use of extensions. Though any implementer can
466
+ * define an extension, there is a set of requirements that SHALL be met
467
+ * as part of the definition of the extension.
468
+ */
469
+ readonly extension?: Extension[];
470
+
471
+ /**
472
+ * May be used to represent additional information that is not part of
473
+ * the basic definition of the element and that modifies the
474
+ * understanding of the element in which it is contained and/or the
475
+ * understanding of the containing element's descendants. Usually
476
+ * modifier elements provide negation or qualification. To make the use
477
+ * of extensions safe and manageable, there is a strict set of governance
478
+ * applied to the definition and use of extensions. Though any
479
+ * implementer can define an extension, there is a set of requirements
480
+ * that SHALL be met as part of the definition of the extension.
481
+ * Applications processing a resource are required to check for modifier
482
+ * extensions.
483
+ *
484
+ * Modifier extensions SHALL NOT change the meaning of any elements on
485
+ * Resource or DomainResource (including cannot change the meaning of
486
+ * modifierExtension itself).
487
+ */
488
+ readonly modifierExtension?: Extension[];
489
+
490
+ /**
491
+ * Code of the property supported.
492
+ */
493
+ readonly code?: string;
494
+
495
+ /**
496
+ * Operations supported for the property.
497
+ */
498
+ readonly op?: string[];
499
+ }
500
+
501
+ /**
502
+ * Information about the
503
+ * [ValueSet/$expand](valueset-operation-expand.html) operation.
504
+ */
505
+ export interface TerminologyCapabilitiesExpansion {
506
+
507
+ /**
508
+ * Unique id for the element within a resource (for internal references).
509
+ * This may be any string value that does not contain spaces.
510
+ */
511
+ readonly id?: string;
512
+
513
+ /**
514
+ * May be used to represent additional information that is not part of
515
+ * the basic definition of the element. To make the use of extensions
516
+ * safe and manageable, there is a strict set of governance applied to
517
+ * the definition and use of extensions. Though any implementer can
518
+ * define an extension, there is a set of requirements that SHALL be met
519
+ * as part of the definition of the extension.
520
+ */
521
+ readonly extension?: Extension[];
522
+
523
+ /**
524
+ * May be used to represent additional information that is not part of
525
+ * the basic definition of the element and that modifies the
526
+ * understanding of the element in which it is contained and/or the
527
+ * understanding of the containing element's descendants. Usually
528
+ * modifier elements provide negation or qualification. To make the use
529
+ * of extensions safe and manageable, there is a strict set of governance
530
+ * applied to the definition and use of extensions. Though any
531
+ * implementer can define an extension, there is a set of requirements
532
+ * that SHALL be met as part of the definition of the extension.
533
+ * Applications processing a resource are required to check for modifier
534
+ * extensions.
535
+ *
536
+ * Modifier extensions SHALL NOT change the meaning of any elements on
537
+ * Resource or DomainResource (including cannot change the meaning of
538
+ * modifierExtension itself).
539
+ */
540
+ readonly modifierExtension?: Extension[];
541
+
542
+ /**
543
+ * Whether the server can return nested value sets.
544
+ */
545
+ readonly hierarchical?: boolean;
546
+
547
+ /**
548
+ * Whether the server supports paging on expansion.
549
+ */
550
+ readonly paging?: boolean;
551
+
552
+ /**
553
+ * Allow request for incomplete expansions?
554
+ */
555
+ readonly incomplete?: boolean;
556
+
557
+ /**
558
+ * Supported expansion parameter.
559
+ */
560
+ readonly parameter?: TerminologyCapabilitiesExpansionParameter[];
561
+
562
+ /**
563
+ * Documentation about text searching works.
564
+ */
565
+ readonly textFilter?: string;
566
+ }
567
+
568
+ /**
569
+ * Supported expansion parameter.
570
+ */
571
+ export interface TerminologyCapabilitiesExpansionParameter {
572
+
573
+ /**
574
+ * Unique id for the element within a resource (for internal references).
575
+ * This may be any string value that does not contain spaces.
576
+ */
577
+ readonly id?: string;
578
+
579
+ /**
580
+ * May be used to represent additional information that is not part of
581
+ * the basic definition of the element. To make the use of extensions
582
+ * safe and manageable, there is a strict set of governance applied to
583
+ * the definition and use of extensions. Though any implementer can
584
+ * define an extension, there is a set of requirements that SHALL be met
585
+ * as part of the definition of the extension.
586
+ */
587
+ readonly extension?: Extension[];
588
+
589
+ /**
590
+ * May be used to represent additional information that is not part of
591
+ * the basic definition of the element and that modifies the
592
+ * understanding of the element in which it is contained and/or the
593
+ * understanding of the containing element's descendants. Usually
594
+ * modifier elements provide negation or qualification. To make the use
595
+ * of extensions safe and manageable, there is a strict set of governance
596
+ * applied to the definition and use of extensions. Though any
597
+ * implementer can define an extension, there is a set of requirements
598
+ * that SHALL be met as part of the definition of the extension.
599
+ * Applications processing a resource are required to check for modifier
600
+ * extensions.
601
+ *
602
+ * Modifier extensions SHALL NOT change the meaning of any elements on
603
+ * Resource or DomainResource (including cannot change the meaning of
604
+ * modifierExtension itself).
605
+ */
606
+ readonly modifierExtension?: Extension[];
607
+
608
+ /**
609
+ * Expansion Parameter name.
610
+ */
611
+ readonly name?: string;
612
+
613
+ /**
614
+ * Description of support for parameter.
615
+ */
616
+ readonly documentation?: string;
617
+ }
618
+
619
+ /**
620
+ * Identifies a specific implementation instance that is described by the
621
+ * terminology capability statement - i.e. a particular installation,
622
+ * rather than the capabilities of a software program.
623
+ */
624
+ export interface TerminologyCapabilitiesImplementation {
625
+
626
+ /**
627
+ * Unique id for the element within a resource (for internal references).
628
+ * This may be any string value that does not contain spaces.
629
+ */
630
+ readonly id?: string;
631
+
632
+ /**
633
+ * May be used to represent additional information that is not part of
634
+ * the basic definition of the element. To make the use of extensions
635
+ * safe and manageable, there is a strict set of governance applied to
636
+ * the definition and use of extensions. Though any implementer can
637
+ * define an extension, there is a set of requirements that SHALL be met
638
+ * as part of the definition of the extension.
639
+ */
640
+ readonly extension?: Extension[];
641
+
642
+ /**
643
+ * May be used to represent additional information that is not part of
644
+ * the basic definition of the element and that modifies the
645
+ * understanding of the element in which it is contained and/or the
646
+ * understanding of the containing element's descendants. Usually
647
+ * modifier elements provide negation or qualification. To make the use
648
+ * of extensions safe and manageable, there is a strict set of governance
649
+ * applied to the definition and use of extensions. Though any
650
+ * implementer can define an extension, there is a set of requirements
651
+ * that SHALL be met as part of the definition of the extension.
652
+ * Applications processing a resource are required to check for modifier
653
+ * extensions.
654
+ *
655
+ * Modifier extensions SHALL NOT change the meaning of any elements on
656
+ * Resource or DomainResource (including cannot change the meaning of
657
+ * modifierExtension itself).
658
+ */
659
+ readonly modifierExtension?: Extension[];
660
+
661
+ /**
662
+ * Information about the specific installation that this terminology
663
+ * capability statement relates to.
664
+ */
665
+ readonly description?: string;
666
+
667
+ /**
668
+ * An absolute base URL for the implementation.
669
+ */
670
+ readonly url?: string;
671
+ }
672
+
673
+ /**
674
+ * Software that is covered by this terminology capability statement. It
675
+ * is used when the statement describes the capabilities of a particular
676
+ * software version, independent of an installation.
677
+ */
678
+ export interface TerminologyCapabilitiesSoftware {
679
+
680
+ /**
681
+ * Unique id for the element within a resource (for internal references).
682
+ * This may be any string value that does not contain spaces.
683
+ */
684
+ readonly id?: string;
685
+
686
+ /**
687
+ * May be used to represent additional information that is not part of
688
+ * the basic definition of the element. To make the use of extensions
689
+ * safe and manageable, there is a strict set of governance applied to
690
+ * the definition and use of extensions. Though any implementer can
691
+ * define an extension, there is a set of requirements that SHALL be met
692
+ * as part of the definition of the extension.
693
+ */
694
+ readonly extension?: Extension[];
695
+
696
+ /**
697
+ * May be used to represent additional information that is not part of
698
+ * the basic definition of the element and that modifies the
699
+ * understanding of the element in which it is contained and/or the
700
+ * understanding of the containing element's descendants. Usually
701
+ * modifier elements provide negation or qualification. To make the use
702
+ * of extensions safe and manageable, there is a strict set of governance
703
+ * applied to the definition and use of extensions. Though any
704
+ * implementer can define an extension, there is a set of requirements
705
+ * that SHALL be met as part of the definition of the extension.
706
+ * Applications processing a resource are required to check for modifier
707
+ * extensions.
708
+ *
709
+ * Modifier extensions SHALL NOT change the meaning of any elements on
710
+ * Resource or DomainResource (including cannot change the meaning of
711
+ * modifierExtension itself).
712
+ */
713
+ readonly modifierExtension?: Extension[];
714
+
715
+ /**
716
+ * Name the software is known by.
717
+ */
718
+ readonly name?: string;
719
+
720
+ /**
721
+ * The version identifier for the software covered by this statement.
722
+ */
723
+ readonly version?: string;
724
+ }
725
+
726
+ /**
727
+ * Information about the
728
+ * [ConceptMap/$translate](conceptmap-operation-translate.html)
729
+ * operation.
730
+ */
731
+ export interface TerminologyCapabilitiesTranslation {
732
+
733
+ /**
734
+ * Unique id for the element within a resource (for internal references).
735
+ * This may be any string value that does not contain spaces.
736
+ */
737
+ readonly id?: string;
738
+
739
+ /**
740
+ * May be used to represent additional information that is not part of
741
+ * the basic definition of the element. To make the use of extensions
742
+ * safe and manageable, there is a strict set of governance applied to
743
+ * the definition and use of extensions. Though any implementer can
744
+ * define an extension, there is a set of requirements that SHALL be met
745
+ * as part of the definition of the extension.
746
+ */
747
+ readonly extension?: Extension[];
748
+
749
+ /**
750
+ * May be used to represent additional information that is not part of
751
+ * the basic definition of the element and that modifies the
752
+ * understanding of the element in which it is contained and/or the
753
+ * understanding of the containing element's descendants. Usually
754
+ * modifier elements provide negation or qualification. To make the use
755
+ * of extensions safe and manageable, there is a strict set of governance
756
+ * applied to the definition and use of extensions. Though any
757
+ * implementer can define an extension, there is a set of requirements
758
+ * that SHALL be met as part of the definition of the extension.
759
+ * Applications processing a resource are required to check for modifier
760
+ * extensions.
761
+ *
762
+ * Modifier extensions SHALL NOT change the meaning of any elements on
763
+ * Resource or DomainResource (including cannot change the meaning of
764
+ * modifierExtension itself).
765
+ */
766
+ readonly modifierExtension?: Extension[];
767
+
768
+ /**
769
+ * Whether the client must identify the map.
770
+ */
771
+ readonly needsMap?: boolean;
772
+ }
773
+
774
+ /**
775
+ * Information about the
776
+ * [ValueSet/$validate-code](valueset-operation-validate-code.html)
777
+ * operation.
778
+ */
779
+ export interface TerminologyCapabilitiesValidateCode {
780
+
781
+ /**
782
+ * Unique id for the element within a resource (for internal references).
783
+ * This may be any string value that does not contain spaces.
784
+ */
785
+ readonly id?: string;
786
+
787
+ /**
788
+ * May be used to represent additional information that is not part of
789
+ * the basic definition of the element. To make the use of extensions
790
+ * safe and manageable, there is a strict set of governance applied to
791
+ * the definition and use of extensions. Though any implementer can
792
+ * define an extension, there is a set of requirements that SHALL be met
793
+ * as part of the definition of the extension.
794
+ */
795
+ readonly extension?: Extension[];
796
+
797
+ /**
798
+ * May be used to represent additional information that is not part of
799
+ * the basic definition of the element and that modifies the
800
+ * understanding of the element in which it is contained and/or the
801
+ * understanding of the containing element's descendants. Usually
802
+ * modifier elements provide negation or qualification. To make the use
803
+ * of extensions safe and manageable, there is a strict set of governance
804
+ * applied to the definition and use of extensions. Though any
805
+ * implementer can define an extension, there is a set of requirements
806
+ * that SHALL be met as part of the definition of the extension.
807
+ * Applications processing a resource are required to check for modifier
808
+ * extensions.
809
+ *
810
+ * Modifier extensions SHALL NOT change the meaning of any elements on
811
+ * Resource or DomainResource (including cannot change the meaning of
812
+ * modifierExtension itself).
813
+ */
814
+ readonly modifierExtension?: Extension[];
815
+
816
+ /**
817
+ * Whether translations are validated.
818
+ */
819
+ readonly translations?: boolean;
820
+ }