Fujitsu Healthy Living Implementation Guide
1.1.28 - release
Publication Build: This will be filled in by the publication tooling
Official URL: http://ig.fujitsu.com/healthy-living/OperationDefinition/fujitsu-operation-documentreference-docref | Version: 1.1.28 | |||
Active as of 2025-07-09 | Computable Name: Fujitsu DocumentReference |
DocumentReference Operation (文書参照オペレーション)
URL: [base]/DocumentReference/$docref
Parameters
Use | Name | Scope | Cardinality | Type | Binding | Documentation |
IN | patient | 1..1 | id | The id of the patient resource located on the server on which this operation is executed. If there is no match, an empty Bundle is returned | ||
IN | start | 0..1 | dateTime | The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no start date is provided, all documents prior to the end date are in scope. If neither a start date nor an end date is provided, the most recent or current document is in scope. The client SHOULD provide values precise to the second + time offset. | ||
IN | end | 0..1 | dateTime | The date range relates to care dates, not record currency dates - e.g. all records relating to care provided in a certain date range. If no end date is provided, all documents subsequent to the start date are in scope. If neither a start date nor an end date is provided, the most recent or current document is in scope. The client SHOULD provide values precise to the second + time offset. | ||
IN | type | 0..1 | CodeableConcept | The type of document being requested. It relates to document type, e.g. the LOINC code for a C-CDA Continuity of Care Document (CCD) is 34133-9 (Summary of episode note). If no type is provided, a CDA document, if available, SHOULD be in scope and all other document types MAY be in scope | ||
IN | on-demand | 0..1 | boolean | This on-demand parameter allows client to dictate whether they are requesting only 'on-demand' or both 'on-demand' and 'stable' documents (or delayed/deferred assembly) that meet the query parameters | ||
IN | pofile | 0..1 | canonical | This parameter allows the client to request documents according to a specific profile, using the the profile's canonical reference | ||
OUT | return | 1..1 | Bundle | The bundle type is "searchset"containing DocumentReference resources which SHOULD conform to the IPA profile of DocumentReference |