- 1. Request
- [Moved at the request of the patient. ( HL7V3.0 )] (UMLS (HL7) C1553397) =Idea or Concept =TransferActReason;
| - 15. Required
- (UMLS (HL7) C1556066) =Idea or Concept =Escort Required;
|
- 2. request
- [A request or order for a service is an intent directed from a placer (request author) to a fulfiller (service performer). Rationale: The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request." Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept. The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request. ( HL7V3.0 )] (UMLS (HL7) C1553888) =Idea or Concept =intent;
| - 16. required
- [A signature for the service is required of this actor. ( HL7V3.0 )] (UMLS (HL7) C1546857) =Intellectual Product =ParticipationSignature;
|
- 3. Request
- [Express the need or desire for; ask for. ( NCI )] (UMLS (NCI) C1272683) Requested =Functional Concept
| - 17. Required
- [The message element must appear every time the message is communicated, but the value may be communicated as null. ( HL7V3.0 )] (UMLS (HL7) C1619636) =Intellectual Product =InclusionNotMandatory;
|
- 4. Request clinical information
- (UMLS (HL7) C1548104) =Idea or Concept =Message type;
| - 18. Required association missing
- [Required association missing in message; or the sequence of the classes is different than required by the standard or one of the conformance profiles identified in the message. ( HL7V3.0 )] (UMLS (HL7) C1699005) =Functional Concept =AcknowledgementDetailSyntaxErrorCode;
|
- 5. REQUEST EXPERT EVIDENCE
- [ ] (UMLS (ICD9CM) C0260846) =Finding
| - 19. Required attribute missing
- [A required attribute is missing in a class. ( HL7V3.0 )] (UMLS (HL7) C1696162) =Functional Concept =AcknowledgementDetailSyntaxErrorCode;
|
- 6. Request for Proposals
- [In a Request for Proposals (RFPs) the Government states work to be undertaken or a problem to be solved. Respondents compete for a common requirement open to all eligible offerors/bidders. Proposals are evaluated using technical and business evaluation criteria and generally involve negotiations. Bids are awarded to the bidder who is responsible and offers the lowest overall price. (from Acquisition Program) ( NCI )] (UMLS (NCI) C0035164) =Intellectual Product ;
| - 20. Required field missing
- (UMLS (HL7) C1549937) =Intellectual Product =Message error condition codes;
|
- 7. Request for Remain Anonymous
- (UMLS (HL7) C1548913) =Health Care Activity =Consent Type;
| - 21. Required intervention to prevent permanent impairment/damage
- (UMLS (HL7) C1546955) =Idea or Concept =Event Consequence;
|
- 8. Request patient authorization
- (UMLS (HL7) C1548103) =Idea or Concept =Message type;
| - 22. Required may be empty
- [Pursuant to a profile or vendor conformance claim, the message element must appear every time the message is communicated, but the value may be communicated as null. ( HL7V3.0 )] (UMLS (HL7) C1554076) =Idea or Concept =Not required;
|
- 9. Request patient demographics
- (UMLS (HL7) C1548106) =Idea or Concept =Message type;
| - 23. Requires crib
- [A crib is required to move the person ( HL7V3.0 )] (UMLS (HL7) C1553395) =Idea or Concept =Mobility impaired;
|
- 10. Request patient information
- (UMLS (HL7) C1548105) =Idea or Concept =Message type;
| - 24. Requires crutches
- [Person requires crutches to ambulate ( HL7V3.0 )] (UMLS (HL7) C1553391) =Finding =Mobility impaired;
|
- 11. Request received
- (UMLS (HL7) C1548257) =Intellectual Product =Order control codes;
| - 25. Requires gurney
- [A gurney is required to move the person ( HL7V3.0 )] (UMLS (HL7) C1553394) =Idea or Concept =Mobility impaired;
|
- 12. Request to dispense blood product
- (UMLS (HL7) C1548991) =Idea or Concept =Blood Product Dispense Status;
| - 26. Requires walker
- [Person requires a walker to ambulate ( HL7V3.0 )] (UMLS (HL7) C1553392) =Idea or Concept =Mobility impaired;
|
- 13. Request to Restrict Access/Disclosure to Medical Record/Protected Health Information
- (UMLS (HL7) C1548912) =Health Care Activity =Consent Type;
| - 27. Requires wheelchair
- [Person requires a wheelchair to be ambulatory ( HL7V3.0 )] (UMLS (HL7) C1553393) =Idea or Concept =Mobility impaired;
|
- 14. Requested information
- (UMLS (HL7) C1546925) =Temporal Concept =Report timing;
| |
home
