@medplum/fhirtypes 0.9.1 → 0.9.4

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.
package/README.md CHANGED
@@ -4,6 +4,8 @@ This library contains [TypeScript](https://www.typescriptlang.org/) type definit
4
4
 
5
5
  ## Installation
6
6
 
7
+ Add as a dependency:
8
+
7
9
  ```bash
8
10
  npm install --save-dev @medplum/fhirtypes
9
11
  ```
@@ -12,7 +14,7 @@ npm install --save-dev @medplum/fhirtypes
12
14
 
13
15
  Consider the following untyped code:
14
16
 
15
- ```typescript
17
+ ```ts
16
18
  const myPatient = {
17
19
  resourceType: 'Patient',
18
20
  name: 'George Washington',
@@ -23,7 +25,7 @@ Keen observers will note that `Patient.name` should not be a string. Instead, it
23
25
 
24
26
  Let's add the type definition and see what happens:
25
27
 
26
- ```typescript
28
+ ```ts
27
29
  import { Patient } from '@medplum/fhirtypes';
28
30
 
29
31
  const myPatient: Patient = {
@@ -42,7 +44,7 @@ And now you will receive typeahead support:
42
44
 
43
45
  So we can build a well-formed example:
44
46
 
45
- ```typescript
47
+ ```ts
46
48
  import { Patient } from '@medplum/fhirtypes';
47
49
 
48
50
  const myPatient: Patient = {
@@ -56,6 +58,10 @@ const myPatient: Patient = {
56
58
  };
57
59
  ```
58
60
 
61
+ ## About Medplum
62
+
63
+ Medplum is a healthcare platform that helps you quickly develop high-quality compliant applications. Medplum includes a FHIR server, React component library, and developer app.
64
+
59
65
  ## License
60
66
 
61
67
  Apache 2.0. Copyright © Medplum 2022
@@ -72,10 +72,16 @@ export interface AccessPolicyResource {
72
72
  resourceType?: string;
73
73
 
74
74
  /**
75
- * Optional compartment restriction for the resource type.
75
+ * DEPRECATED Optional compartment restriction for the resource type.
76
76
  */
77
77
  compartment?: Reference;
78
78
 
79
+ /**
80
+ * The rules that the server should use to determine which resources to
81
+ * allow.
82
+ */
83
+ criteria?: string;
84
+
79
85
  /**
80
86
  * Optional flag to indicate that the resource type is read-only.
81
87
  */
@@ -15,6 +15,7 @@ import { ProdCharacteristic } from './ProdCharacteristic';
15
15
  import { ProductShelfLife } from './ProductShelfLife';
16
16
  import { Quantity } from './Quantity';
17
17
  import { Reference } from './Reference';
18
+ import { RelatedArtifact } from './RelatedArtifact';
18
19
  import { Resource } from './Resource';
19
20
 
20
21
  /**
@@ -227,6 +228,17 @@ export interface DeviceDefinition {
227
228
  * made.
228
229
  */
229
230
  material?: DeviceDefinitionMaterial[];
231
+
232
+ /**
233
+ * What kind of device or device system this is.
234
+ */
235
+ classification?: DeviceDefinitionClassification[];
236
+
237
+ /**
238
+ * Indicates the anotomic location on the subject's body where the device
239
+ * was used ( i.e. the target).
240
+ */
241
+ bodySite?: CodeableConcept;
230
242
  }
231
243
 
232
244
  /**
@@ -280,6 +292,58 @@ export interface DeviceDefinitionCapability {
280
292
  description?: CodeableConcept[];
281
293
  }
282
294
 
295
+ /**
296
+ * What kind of device or device system this is.
297
+ */
298
+ export interface DeviceDefinitionClassification {
299
+
300
+ /**
301
+ * Unique id for the element within a resource (for internal references).
302
+ * This may be any string value that does not contain spaces.
303
+ */
304
+ id?: string;
305
+
306
+ /**
307
+ * May be used to represent additional information that is not part of
308
+ * the basic definition of the element. To make the use of extensions
309
+ * safe and manageable, there is a strict set of governance applied to
310
+ * the definition and use of extensions. Though any implementer can
311
+ * define an extension, there is a set of requirements that SHALL be met
312
+ * as part of the definition of the extension.
313
+ */
314
+ extension?: Extension[];
315
+
316
+ /**
317
+ * May be used to represent additional information that is not part of
318
+ * the basic definition of the element and that modifies the
319
+ * understanding of the element in which it is contained and/or the
320
+ * understanding of the containing element's descendants. Usually
321
+ * modifier elements provide negation or qualification. To make the use
322
+ * of extensions safe and manageable, there is a strict set of governance
323
+ * applied to the definition and use of extensions. Though any
324
+ * implementer can define an extension, there is a set of requirements
325
+ * that SHALL be met as part of the definition of the extension.
326
+ * Applications processing a resource are required to check for modifier
327
+ * extensions.
328
+ *
329
+ * Modifier extensions SHALL NOT change the meaning of any elements on
330
+ * Resource or DomainResource (including cannot change the meaning of
331
+ * modifierExtension itself).
332
+ */
333
+ modifierExtension?: Extension[];
334
+
335
+ /**
336
+ * A classification or risk class of the device model.
337
+ */
338
+ type?: CodeableConcept;
339
+
340
+ /**
341
+ * Further information qualifying this classification of the device
342
+ * model.
343
+ */
344
+ justification?: RelatedArtifact[];
345
+ }
346
+
283
347
  /**
284
348
  * A name given to the device to identify it.
285
349
  */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@medplum/fhirtypes",
3
- "version": "0.9.1",
3
+ "version": "0.9.4",
4
4
  "description": "Medplum FHIR Type Definitions",
5
5
  "author": "Medplum <hello@medplum.com>",
6
6
  "license": "Apache-2.0",