This page is part of the electronic Case Reporting (eCR) (v0.1.0: STU 1 Ballot 1) based on FHIR R3. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions 
SD.10 StructureDefinition-eicr-procedurerequest
source file: source/pages/_includes/eicr-procedurerequest-intro.md
ECR Profile: eICR Lab Orders Profile
Scope and Usage
The Electronic Case Reporting Lab Orders profile establishes the core elements, extensions, vocabularies and value sets for representing the following for electronic case reporting:
- Initial Case Report laboratory orders and other diagnostics for the reported event.
Additional Profile specific implementation guidance:
- None
Examples
SD.10.1 Formal Views of Profile Content
Description of Profiles, Differentials, and Snapshots.
The official URL for this profile is: http://fhir.hl7.org/us/ecr/StructureDefinition/eicr-procedurerequest
Published on Wed Nov 29 00:00:00 AEDT 2017 as a draft by .
This profile builds on ProcedureRequest
Differential View
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
  ProcedureRequest | 0..* | Ordered tests | ||
 identifier | S | 0..* | Identifier | |
 code | S | 1..1 | CodeableConcept | Binding: LOINC Diagnostic Report Codes (extensible) |
| Documentation for this format | ||||
Snapshot View
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| ProcedureRequest | I | 0..* | Ordered tests | |
 id | Σ | 0..1 | id | Logical id of this artifact |
 meta | Σ | 0..1 | Meta | Metadata about the resource |
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created |
| language | 0..1 | code | Language of the resource content Binding: Common Languages (extensible) | |
| text | I | 0..1 | Narrative | Text summary of the resource, for human interpretation |
 contained | 0..* | Resource | Contained, inline Resources | |
 extension | 0..* | Extension | Additional Content defined by implementations | |
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored |
| identifier | SΣ | 0..* | Identifier | Identifiers assigned to this order |
 definition | Σ | 0..* | Reference(ActivityDefinition), Reference(PlanDefinition) | Protocol or definition |
| basedOn | Σ | 0..* | Reference(Resource) | What request fulfills |
| replaces | Σ | 0..* | Reference(Resource) | What request replaces |
| requisition | Σ | 0..1 | Identifier | Composite Request ID |
| status | ?!Σ | 1..1 | code | draft | active | suspended | completed | entered-in-error | cancelled Binding: RequestStatus (required) |
| intent | ?!Σ | 1..1 | code | proposal | plan | order + Binding: RequestIntent (required) |
| priority | Σ | 0..1 | code | routine | urgent | asap | stat Binding: RequestPriority (required) |
| doNotPerform | ?!Σ | 0..1 | boolean | True if procedure should not be performed |
| category | Σ | 0..* | CodeableConcept | Classification of procedure Binding: Procedure Category Codes (SNOMED CT) (example) |
| code | SΣ | 1..1 | CodeableConcept | What is being requested/ordered Binding: LOINC Diagnostic Report Codes (extensible) |
| subject | Σ | 1..1 | Reference(Patient), Reference(Group), Reference(Location), Reference(Device) | Individual the service is ordered for |
| context | Σ | 0..1 | Reference(Encounter), Reference(EpisodeOfCare) | Encounter or Episode during which request was created |
 occurrence[x] | Σ | 0..1 | dateTime, Period, Timing | When procedure should occur |
| asNeeded[x] | Σ | 0..1 | boolean, CodeableConcept | Preconditions for procedure or diagnostic Binding: SNOMED CT Medication As Needed Reason Codes (example) |
| authoredOn | Σ | 0..1 | dateTime | Date request signed |
| requester | ΣI | 0..1 | BackboneElement | Who/what is requesting procedure or diagnostic |
 id | 0..1 | string | xml:id (or equivalent in JSON) | |
| extension | 0..* | Extension | Additional Content defined by implementations | |
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored |
| agent | Σ | 1..1 | Reference(Device), Reference(Practitioner), Reference(Organization) | Individual making the request |
| onBehalfOf | Σ | 0..1 | Reference(Organization) | Organization agent is acting for |
| performerType | Σ | 0..1 | CodeableConcept | Performer role Binding: Participant Roles (example) |
| performer | Σ | 0..1 | Reference(Practitioner), Reference(Organization), Reference(Patient), Reference(Device), Reference(RelatedPerson), Reference(HealthcareService) | Requested perfomer |
| reasonCode | Σ | 0..* | CodeableConcept | Explanation/Justification for test Binding: Procedure Reason Codes (example) |
| reasonReference | Σ | 0..* | Reference(Condition), Reference(Observation) | Explanation/Justification for test |
| supportingInfo | 0..* | Reference(Resource) | Additional clinical information | |
| specimen | Σ | 0..* | Reference(Specimen) | Procedure Samples |
| bodySite | Σ | 0..* | CodeableConcept | Location on Body Binding: SNOMED CT Body Structures (example) |
| note | 0..* | Annotation | Comments | |
| relevantHistory | 0..* | Reference(Provenance) | Request provenance | |
| Documentation for this format | ||||
Downloads: StructureDefinition: (XML, JSON), Schema: XML Schematron
SD.10.2 Quick Start
Below is an overview of the required set of RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.
...todo...
