FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions icon

12.18.7 Resource ServiceRequest - Examples

Orders and Observations icon Work GroupMaturity Level: N/AStandards Status: InformativeSecurity Category: Patient Compartments: Device, Encounter, Patient, Practitioner, RelatedPerson


An introduction to this page as well as proper examples are to be submitted shortly.

Example Name id Format
Lipid Panel Order lipid XML JSON Turtle
CT Scan order di XML JSON Turtle
Glucose Monitoring glucose XML JSON Turtle
Continuous Glucose Monitoring continuous-glucose XML JSON Turtle
Free T4 Add on Order ft4 XML JSON Turtle
An example of a Head CT procedure example XML JSON Turtle
Example with sub-requests derived from the request subrequest XML JSON Turtle
An example of an order for home physiotherapy physiotherapy XML JSON Turtle
An example of an order for physical therapy with a ratio quantity physicaltherapy XML JSON Turtle
An example of an order to not turn a patient do-not-turn XML JSON Turtle
Part of an exercise plan benchpress XML JSON Turtle
Example of an order for an implant example-implant XML JSON Turtle
Example of an order for anambulation procedure ambulation XML JSON Turtle
Example of an order for a biopsy procedure that was part of a colonoscopy colon-biopsy XML JSON Turtle
Example of an order for a colonoscopy procedure with complication colonoscopy XML JSON Turtle
Example of an order for an appendectomy procedure that is primarily narrative appendectomy-narrative XML JSON Turtle
Example of an order for an obstetric procedure ob XML JSON Turtle
Example of an order for a physical therapy evaluation procedure physical-therapy XML JSON Turtle
Example of an order for patient education education XML JSON Turtle
An example of a Myringotomy referral request myringotomy XML JSON Turtle
Order for mechanical ventilation with order details vent XML JSON Turtle
 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.