| # | Name | Location | Type | Details | Index | Description |
|---|---|---|---|---|---|---|
| .01 | request number(+) | 0;1 | FREE TEXT | B | Request number is automatically generated by the system and is used to identify a specific CMOR request. When a request is transmitted to another station, the request number remains the same across both stations. | |
| .02 | requested by(+) | 0;2 | POINTER | 200 | AD | The REQUESTED BY field will exist at the originating station only. Once the request is transmitted to another station, the receiving station will not have data in this field. This is due to the fact that the receiving location will not have the originating person in their New Person (#200) file. |
| .03 | date requested(+) | 0;3 | DATE-TIME | Date requested is the date the request was entered into the system. | ||
| .04 | patient | 0;4 | POINTER | 2 | C | Patient affected by the CMOR change request. |
| .05 | requestor phone number(+) | 0;5 | FREE TEXT | Phone number that can be used to contact the person requesting the CMOR change request. This data is transmitted to the receiving location and is needed if the person reviewing the request has questions. | ||
| .06 | status(+) | 0;6 | SET OF CODES | 1:OPEN 2:REQUESTED 3:PENDING APPROVAL 4:APPROVED 5:DISAPPROVED | AC | This field tracks the progress of the CMOR change request. As the request is being entered, it has a status of Open. Once the requestor sends the request, the status is change to Requested. At the receiving location, the status is set to Pending Approval. Once it is processed, it will be set to Approved or Disapproved. The requesting site will also update the status to Approved or Disapproved once the request has been processed. |
| .07 | site | 0;7 | POINTER | 4 | At the site that has RECEIVED the Request/Push the site field will be the site that initiated the Request/Push. At the site that has SENT the request it will be the site the request was sent to. | |
| .08 | type of message(+) | 0;8 | SET OF CODES | 1:RECEIVED 2:SENT | A type of sent refers to the CMOR request originated from the station and is being sent to another station. A received type refers to the CMOR request originated from the other station. | |
| .09 | cmor after approval | 0;9 | POINTER | 4 | This field will contain the site that the request is asking to be the CMOR or the site that the Push is making the CMOR. | |
| 1.01 | requestor name | 1;1 | FREE TEXT | The requestor name is a free-text name of the person sending the CMOR request. This field is blank at the originating site since the Request By field points to the person. This field is used at the receiving location. | ||
| 1.02 | reason for request(+) | 1;2 | FREE TEXT | Enter a brief reason for requesting the CMOR transfer. | ||
| 1.03 | type of action(+) | 1;3 | SET OF CODES | 1:REQUEST SENT TO 2:REQUEST RECEIVED FROM 3:PUSH SENT TO 4:PUSH RECEIVED FROM | This field is used to show which request was made and whether it originated at this facility or was received at this facility. | |
| 2.01 | reviewed by | 2;1 | POINTER | 200 | AE | The site processing this request will have this field populated with the user that processed the request. The site that made the request will not have this field populated but will instead have the Reviewer Name field populated. |
| 2.02 | date reviewed | 2;2 | DATE-TIME | This date reflects the date the request was approved or denied. | ||
| 2.03 | reviewer phone number | 2;3 | FREE TEXT | Phone number that is used to contact the person that reviewed and approved or denied the CMOR change request. This data is transmitted to the requesting station and is needed if the person receiving the result has questions. | ||
| 3.01 | reviewer name | 3;1 | FREE TEXT | The reviewer name is a free-text name of the person reviewing the CMOR request. This field is blank at the reviewing site since the Reviewed By field points to the person. This field is used at the originating station and is transmitted along with the result of the request. | ||
| 3.02 | reviewer comments | 3;2 | FREE TEXT | Comments that are entered by the person reviewing the request. These comments are transmitted back to the origination station after the request is approved or denied. | ||
| 100 | days old | COMPUTED | Days old is calculated by comparing the date the request was entered or received and compared to today's date. The number of days between these two dates determines the number of days old a request is. | |||
| 101 | requestor | COMPUTED | The result of this computed field is the comparison of the Request By and the Requestor Name field. Since only one of these two fields exist within a CMOR request, this computed field extracts the one that exists and gives a consistent place to use in print templates for displaying the name | |||
| 102 | reviewer | COMPUTED | The result of this computed field is the comparison of the Reviewed By and the Reviewer Name field. Since only on of these two fields exist within a CMOR request, this computed field extracts the one that exists and gives a consistent place to use in print templates for displaying the name |
Not Referenced