{"text_format":"2","workbook":"xls","n_sheets":13,"sheets":["Sheet1","Burden Statement","Enablement Workbook","Facilities","Pre Questionnaire","Applications","Transaction Volumes","Messages of Interest","Elements of Interest","EOI-Questionnaire","Contacts","Ports","DS Deliverable Checklist"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":3,"defined_names":50,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"Sheet1","index":0,"n_rows":12,"n_cols":3,"rows_kept":12,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
[]
[]
[]
[]
[null,null,"BioSense - Recruitment of Data Sources"]
[null,null," "]
[]
[null,null,"Attachment 3"]
[]
[]
[]
[null,null," BioSense Enablement Preparation Workbook MDS "]

{"sheet":"Burden Statement","index":1,"n_rows":8,"n_cols":1,"rows_kept":8,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["BioSense - Recruitment of Data Sources"]
["BioSense Enablement Preparation Workbook MDS"]
[]
["Form Approved"]
["OMB No.   0920-XXXX"]
["Exp, Date  xx/xx/20xx"]
[]
["Public reporting burden of this collection of information is estimated to average 4 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information.  An agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number.  Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to CDC/ATSDR Reports Clearance Officer; 1600 Clifton Road NE, MS D-74, Atlanta, Georgia 30333; Attn: PRA (0920-XXXX)."]

{"sheet":"Enablement Workbook","index":2,"n_rows":27,"n_cols":2,"rows_kept":27,"cut":false,"hidden":false,"merged":[[4,0,4,1],[5,0,5,1],[6,0,6,1],[11,0,11,1],[8,0,8,1],[7,0,7,1]],"flags":["formulas_cached_only"]}
["Data Source"]
["BioSense Messaging Guide Version","1.05"]
["Data Provisioning Database","ADB200802.01.00"]
[]
["Introduction"]
["Please answer all questions with as much detail as possible in the non-shaded areas."]
["Please answer the questions in the electronic spreadsheet."]
["Except for the Facilities tab, the answers are at the data source level.  Please provide any exceptions at the facility level"]
["Except for the Transaction Volumes tab, the answers are for all patient classes (inpatient, outpatient, emergency).  Please provide any exceptions based on patient class"]
["Feel free to add rows as necessary.  Please do not add columns."]
["Please do not delete rows.  Fill in N/A where applicable."]
["If you have any questions, please contact your BioSense representative."]
[]
["Fields","Descriptions"]
["Available?","Is the item currently available for the BioSense project."]
[]
["Tab","Description"]
["Facilities","Information about the facilites, sites and/or clinics"]
["Pre Questionnaire","Preliminary questions about the data source"]
["Applications","Applications used by the data source"]
["Messages of Interest","BioSense messages of interest"]
["Elements of Interest","BioSense elements of interest"]
["Elements of Interest - Questionnaire","BioSense elements of interest questions."]
["Contacts","Data Source and BioSense contacts"]
["Transaction Volumes","Data Source transaction volumes"]
["Ports","Data Source ports"]
["Checklists","Checklists for requested information from the Data Source"]

{"sheet":"Facilities","index":3,"n_rows":5,"n_cols":14,"rows_kept":5,"cut":false,"hidden":false,"merged":[[0,1,0,2],[2,1,2,2]],"flags":["formulas_cached_only"]}
[null,"Integrator Organization (responsible for assigning the BioSense identifiers)",null,"Address Line 1","Address Line 2","City","State","Zip","Switchboard Phone#","Integrator Organization OID","Party ID","Test Integrator OID","Prod Integrator OID","Column1"]
[{"$nulls":13},"Initial Activation"]
[null,"Parent Organization (sends the data to BioSense on behalf of the organizations/facilities)",null,"Address Line 1","Address Line 2","City","State","Zip","Switchboard Phone#","Business Parent OID","Party ID",null,null,"Post Activation"]
[{"$nulls":13},"Post Certification"]
["Facility Number","Hospital Organization (Business 'parent')","Hospital Facility","Address Line 1","Address Line 2","City","State","Zip","Switchboard Phone#","Facility OID","CLIA Number \n(for reporting Labs)","Data Source Facility ID \n(as seen in messages)","Comments"]

{"sheet":"Pre Questionnaire","index":4,"n_rows":191,"n_cols":15,"rows_kept":191,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Data Category","Element Category","Q#","Question","Answer","Comments","Question1","Question2","Question3","Question4","Question5","CategoryOrder","QKey","Data Source","Category Key"]
["Facility"]
[null,"General"]
[null,null,1,"Are there any constraints that might limit, impede or prohibit the project in any way?  If so, please list and explain.  \nExample: Development of census interface by data source can not begin until a PO has been signed.\nExample: Resource Contraints ",null,null,"Are there any constraints that might limit, impede or prohibit the project in any way?  If so, please list and explain.  \nExample: Development of census interface by data source can not begin until a PO has been signed.\nExample: Resource Contraints ",{"$nulls":4},1,34,"<Data Source>",1]
[null,null,2,"Is there a formal software Change Control process?  If so, please provide the appropriate details, such as timeline requirements, points of contact, etc.  ",null,null,"Is there a formal software Change Control process?  If so, please provide the appropriate details, such as timeline requirements, points of contact, etc.  ",{"$nulls":4},1,35,"<Data Source>",1]
[null,null,null,""]
[null,null,3,"Is there an average cost per full-time employee (FTE) for project costing purposes?\nFor example, if the cost per FTE is $50 an hour.  And the project maintenance requires 1 hour of 1 FTE per week.  Then we know to budget approximately $200 per month for maintenance",null,null,"Is there an average cost per full-time employee (FTE) for project costing purposes?\nFor example, if the cost per FTE is $50 an hour.  And the project maintenance requires 1 hour of 1 FTE per week.  Then we know to budget approximately $200 per month"," for maintenance",null,null,null,1,37,"<Data Source>",1]
[null,null,4,"Are there scheduled service interruptions?  Daily/weekly/monthly",null,null,"Are there scheduled service interruptions?  Daily/weekly/monthly",{"$nulls":4},1,40,"<Data Source>",1]
[null,null,null,""]
[null,null,5,"Does the organization contract out development? ",null,null,"Does the organization contract out development? ",{"$nulls":4},1,41,"<Data Source>",1]
[null,null,6,"Are some or all of the applications or integration services outsourced?",null,null,"Are some or all of the applications or integration services outsourced?",{"$nulls":4},1,42,"<Data Source>",1]
[null,null,null,""]
[null,null,7,"Will HIS send data for patients outside the organization?   (e.g. Nursing home visits) If yes, how will they be identified?",null,null,"Will HIS send data for patients outside the organization?   (e.g. Nursing home visits) If yes, how will they be identified?",{"$nulls":4},1,26,"<Data Source>",1]
[null,null,8,"Do all of the interfaced ancillary systems process merges?\nFor example, if the ADT system sends a patient merge, can the Lab system process the merge or is this done manually?",null,null,"Do all of the interfaced ancillary systems process merges?\nFor example, if the ADT system sends a patient merge, can the Lab system process the merge or is this done manually?",{"$nulls":4},1,28,"<Data Source>",1]
[null,null,null,""]
[null,null,9,"Do patients get a different account number for each visit (episode of care)?\nIf not, how can we determine distinct episodes of care in the HL7 messages.\nExample: Recurring outpatients",null,null,"Do patients get a different account number for each visit (episode of care)?\nIf not, how can we determine distinct episodes of care in the HL7 messages.\nExample: Recurring outpatients",{"$nulls":4},1,29,"<Data Source>",1]
[null,null,10,"Who is the administrator (access control) for the BioSense information?",null,null,"Who is the administrator (access control) for the BioSense information?",{"$nulls":4},1,138,"<Data Source>",1]
[null,null,null,""]
[null,null,11,"Will your HIS send outside patients?  If yes, how are outside patients determined?  For example, Pre-employment physicials, lab only patient from an external lab.",null,null,"Will your HIS send outside patients?  If yes, how are outside patients determined?  For example, Pre-employment physicials, lab only patient from an external lab.",{"$nulls":4},1,145,"<Data Source>",1]
[null,null,99,"Additional Facility General Notes?",null,null,"Additional Facility General Notes?",{"$nulls":4},1,163,"<Data Source>",1]
["Facility",null,null,""]
[null,"Multiple",null,""]
[null,null,null,""]
[null,null,1,"Is there an enterprise MRN utilized in all messages?",null,null,"Is there an enterprise MRN utilized in all messages?",{"$nulls":4},2,164,"<Data Source>",2]
[null,null,2,"Do any facilities share assigning authorities for the MRN?",null,null,"Do any facilities share assigning authorities for the MRN?",{"$nulls":4},2,146,"<Data Source>",2]
[null,null,null,""]
[null,null,3,"Do any facilities share assigning authorities for the Account numbers?",null,null,"Do any facilities share assigning authorities for the Account numbers?",{"$nulls":4},2,136,"<Data Source>",2]
[null,null,4,"Are the in-house support resources the same for all facilities?",null,null,"Are the in-house support resources the same for all facilities?",{"$nulls":4},2,14,"<Data Source>",2]
[null,null,null,""]
[null,null,5,"Are the codes (master files) for ADT, Lab, Rad, RX, etc the same across all facilities?",null,null,"Are the codes (master files) for ADT, Lab, Rad, RX, etc the same across all facilities?",{"$nulls":4},2,11,"<Data Source>",2]
[null,null,6,"Are MRNs unique across facilities?",null,null,"Are MRNs unique across facilities?",{"$nulls":4},2,16,"<Data Source>",2]
[null,null,null,""]
[null,null,7,"Are Account Numbers unique across facilities?",null,null,"Are Account Numbers unique across facilities?",{"$nulls":4},2,17,"<Data Source>",2]
[null,null,8,"Are nursing units unique across facilities?",null,null,"Are nursing units unique across facilities?",{"$nulls":4},2,18,"<Data Source>",2]
[null,null,null,""]
[null,null,99,"Additional Multiple Facility Notes?",null,null,"Additional Multiple Facility Notes?",{"$nulls":4},2,33,"<Data Source>",2]
["Interface",null,null,""]
[null,"All",null,""]
[null,null,1,"Are there any integration environment standards of which the BioSense Implementation Team needs to be aware?  ",null,null,"Are there any integration environment standards of which the BioSense Implementation Team needs to be aware?  ",{"$nulls":4},3,55,"<Data Source>",5]
[null,null,null,""]
[null,null,2,"Are there any special process and functions in your interface environment that might impact this project?  For example: Timing of batch processing, special external scripts, FTP, etc.  If so, please list them and provide a brief explanation",null,null,"Are there any special process and functions in your interface environment that might impact this project?  For example: Timing of batch processing, special external scripts, FTP, etc.  If so, please list them and provide a brief explanation",{"$nulls":4},3,56,"<Data Source>",5]
[null,null,3,"Does the organization have special facilities that need to be excluded (psych hospital etc)?",null,null,"Does the organization have special facilities that need to be excluded (psych hospital etc)?",{"$nulls":4},3,19,"<Data Source>",5]
[null,null,null,""]
[null,null,4,"Do any of the interfaced applications typically imbed the patient identifiable information in any field outside of the PID segment?  \nFor example, in order/result free-text fields, placer/filler order numbers, etc.",null,null,"Do any of the interfaced applications typically imbed the patient identifiable information in any field outside of the PID segment?  \nFor example, in order/result free-text fields, placer/filler order numbers, etc.",{"$nulls":4},3,59,"<Data Source>",5]
[null,null,5,"Do any field codes have “special” meanings?  For example, “TBD” may mean “To Be Determined” or “9999” may mean “For Departmental Purposes Only” or \"CD: xxxx\" means a code has not been set up",null,null,"Do any field codes have “special” meanings?  For example, “TBD” may mean “To Be Determined” or “9999” may mean “For Departmental Purposes Only” or \"CD: xxxx\" means a code has not been set up",{"$nulls":4},3,61,"<Data Source>",5]
[null,null,null,""]
[null,null,6,"What are the standard procedures for updating master files?  When is it done?  By whom?  Is it done on a timely basis?  How is the need for a change identified?",null,null,"What are the standard procedures for updating master files?  When is it done?  By whom?  Is it done on a timely basis?  How is the need for a change identified?",{"$nulls":4},3,64,"<Data Source>",5]
[null,null,7,"Is the set ID numbering scheme sequential starting at 1, incrementing by 1 or does it have a numbering scheme?  For example, if OBR-1 is 99, it has a special meaning. ",null,null,"Is the set ID numbering scheme sequential starting at 1, incrementing by 1 or does it have a numbering scheme?  For example, if OBR-1 is 99, it has a special meaning. ",{"$nulls":4},3,65,"<Data Source>",5]
[null,null,null,""]
[null,null,8,"How does the organization want to exclude special patients (psych patients, HIV patients, celebrities, etc) for the BioSense project?  If so, how are these special patients identified in messages? ",null,null,"How does the organization want to exclude special patients (psych patients, HIV patients, celebrities, etc) for the BioSense project?  If so, how are these special patients identified in messages? ",{"$nulls":4},3,66,"<Data Source>",5]
[null,null,9,"Does the interface engine wait to accepts an acknowledgment before sending the next message?",null,null,"Does the interface engine wait to accepts an acknowledgment before sending the next message?",{"$nulls":4},3,68,"<Data Source>",5]
[null,null,null,""]
[null,null,10,"Are timezones used in message timestamp fields?  If so, are they based upon the hospital, e.g., the location of what triggered the message?  Interface engine?",null,null,"Are timezones used in message timestamp fields?  If so, are they based upon the hospital, e.g., the location of what triggered the message?  Interface engine?",{"$nulls":4},3,72,"<Data Source>",5]
[null,null,11,"Are there any messages that should be filtered out from the production data stream for any reason (test messages, known errors, etc).",null,null,"Are there any messages that should be filtered out from the production data stream for any reason (test messages, known errors, etc).",{"$nulls":4},3,73,"<Data Source>",5]
[null,null,null,""]
[null,null,12,"Does the ACK have any special requirements outside the HL7 standard?\nFor example, the engine verifies that the MSH-10 (message control number) is sequential from the previous message.",null,null,"Does the ACK have any special requirements outside the HL7 standard?\nFor example, the engine verifies that the MSH-10 (message control number) is sequential from the previous message.",{"$nulls":4},3,137,"<Data Source>",5]
[null,null,13,"Are ORC-2 and ORC-3 the same values/length between the HIS and Lab/RAD systems.  For example, the HIS system has \"12345\" and the Lab system has \"12345-0625\".  The Lab system value will have to be truncated to match the HIS system value. ",null,null,"Are ORC-2 and ORC-3 the same values/length between the HIS and Lab/RAD systems.  For example, the HIS system has \"12345\" and the Lab system has \"12345-0625\".  The Lab system value will have to be truncated to match the HIS system value. ",{"$nulls":4},3,141,"<Data Source>",5]
[null,null,null,""]
[null,null,14,"Are OBX sent in ADT messages?  If so, please define?  Typcially these segments are dropped unless there is some clinical relevance.  For example, some sites may actually send discharge diagnosis or other site-defined information in an OBX-segment.",null,null,"Are OBX sent in ADT messages?  If so, please define?  Typcially these segments are dropped unless there is some clinical relevance.  For example, some sites may actually send discharge diagnosis or other site-defined information in an OBX-segment.",{"$nulls":4},3,144,"<Data Source>",5]
[null,null,15,"Do your interfaces allow the use of & (subcomponent separator) in fields that means 'and'.  Note: If so, the data engine will need to fix this in their engine as the BioSense Integrator engine and the CDC processing would strip out the parts after the separator.",null,null,"Do your interfaces allow the use of & (subcomponent separator) in fields that means 'and'.  Note: If so, the data engine will need to fix this in their engine as the BioSense Integrator engine and the CDC processing would strip out the parts after th","e separator.",null,null,null,3,194,"<Data Source>",5]
[null,null,null,""]
[null,null,99,"Additional Interfaces All Notes?",null,null,"Additional Interfaces All Notes?",{"$nulls":4},3,75,"<Data Source>",5]
["Interface - ED/Clinical",null,null,""]
[null,"All",null,""]
[null,null,1,"Are the ED/Clinical applications the same across all facilities?",null,null,"Are the ED/Clinical applications the same across all facilities?",{"$nulls":4},4,165,"<Data Source>",8]
[null,null,null,""]
[null,null,2,"Are the ED/Clinical application versions the same across all facilities?",null,null,"Are the ED/Clinical application versions the same across all facilities?",{"$nulls":4},4,166,"<Data Source>",8]
[null,null,3,"Are the ED/Clinical application interface specifications the same across all facilities?",null,null,"Are the ED/Clinical application interface specifications the same across all facilities?",{"$nulls":4},4,167,"<Data Source>",8]
[null,null,null,""]
[null,null,4,"If there isn't an outbound HL7 interface, is there a report generated out of the ED system?  PDF, Textual HL7 messages, text files?",null,null,"If there isn't an outbound HL7 interface, is there a report generated out of the ED system?  PDF, Textual HL7 messages, text files?",{"$nulls":4},4,168,"<Data Source>",8]
[null,null,99,"Additional ED/Clinical Notes?",null,null,"Additional ED/Clinical Notes?",{"$nulls":4},4,10,"<Data Source>",8]
["Interface - Foundational",null,null,""]
[null,"Demographic Data",null,""]
[null,null,null,""]
[null,null,1,"Are the ADT applications the same across all facilities?",null,null,"Are the ADT applications the same across all facilities?",{"$nulls":4},5,169,"<Data Source>",11]
[null,null,2,"Are the ADT application versions the same across all facilities?",null,null,"Are the ADT application versions the same across all facilities?",{"$nulls":4},5,170,"<Data Source>",11]
[null,null,null,""]
[null,null,3,"Are the ADT application interface specifications the same across all facilities?",null,null,"Are the ADT application interface specifications the same across all facilities?",{"$nulls":4},5,171,"<Data Source>",11]
[null,null,99,"Additional Foundational Demographics Information?",null,null,"Additional Foundational Demographics Information?",{"$nulls":4},5,149,"<Data Source>",11]
["Interface - Foundational",null,null,""]
[null,"Hospital Census/Utilization",null,""]
[null,null,null,""]
[null,null,1,"Will the Census come in as a file or tcp/ip?",null,null,"Will the Census come in as a file or tcp/ip?",{"$nulls":4},9,129,"<Data Source>",10]
[null,null,99,"Additional Foundational Hospital Census/Utilization information?",null,null,"Additional Foundational Hospital Census/Utilization information?",{"$nulls":4},9,157,"<Data Source>",10]
["Interface - Lab/Micro",null,null,""]
[null,"Orders",null,""]
[null,null,null,""]
[null,null,1,"Are the Lab Orders applications the same across all facilities/labs?",null,null,"Are the Lab Orders applications the same across all facilities/labs?",{"$nulls":4},10,175,"<Data Source>",13]
[null,null,2,"Are the Lab Orders application versions the same across all facilities/labs?",null,null,"Are the Lab Orders application versions the same across all facilities/labs?",{"$nulls":4},10,176,"<Data Source>",13]
[null,null,null,""]
[null,null,3,"Are the Lab Orders application interface specifications the same across all facilities/labs?",null,null,"Are the Lab Orders application interface specifications the same across all facilities/labs?",{"$nulls":4},10,193,"<Data Source>",13]
[null,null,99,"Additional Lab/Micro Orders Notes?",null,null,"Additional Lab/Micro Orders Notes?",{"$nulls":4},10,150,"<Data Source>",13]
["Interface - Lab/Micro",null,null,""]
[null,"Results",null,""]
[null,null,null,""]
[null,null,1,"Are the Lab Results applications the same across all facilities/labs?",null,null,"Are the Lab Results applications the same across all facilities/labs?",{"$nulls":4},11,177,"<Data Source>",14]
[null,null,2,"Are the Lab Results application versions the same across all facilities/labs?",null,null,"Are the Lab Results application versions the same across all facilities/labs?",{"$nulls":4},11,178,"<Data Source>",14]
[null,null,null,""]
[null,null,3,"Are the Lab Results application interface specifications the same across all facilities/labs?",null,null,"Are the Lab Results application interface specifications the same across all facilities/labs?",{"$nulls":4},11,179,"<Data Source>",14]
[null,null,4,"For Micro results, do the subtests (secondary Order groups) under the main test (first Order group) reflect the main group?\nExample: Test of urine culture.  Result test of specimen description, gram stain, colony count, and organism.  ",null,null,"For Micro results, do the subtests (secondary Order groups) under the main test (first Order group) reflect the main group?\nExample: Test of urine culture.  Result test of specimen description, gram stain, colony count, and organism.  ",{"$nulls":4},11,139,"<Data Source>",14]
[null,null,null,""]
[null,null,5,"If current lab results interface is not discrete/computable (but human readable), can we explore the possibility of obtaining the discrete interface as part of this project?",null,null,"If current lab results interface is not discrete/computable (but human readable), can we explore the possibility of obtaining the discrete interface as part of this project?",{"$nulls":4},11,5,"<Data Source>",14]
[null,null,6,"Are notes sent in NTE segment(s) or via OBX segments(s).  If the latter, is the OBX sub-ID (OBX-4) utilized?",null,null,"Are notes sent in NTE segment(s) or via OBX segments(s).  If the latter, is the OBX sub-ID (OBX-4) utilized?",{"$nulls":4},11,180,"<Data Source>",14]
[null,null,null,""]
[null,null,99,"Additional Lab/Micro Results Notes?",null,null,"Additional Lab/Micro Results Notes?",{"$nulls":4},11,159,"<Data Source>",14]
["Interface - Pharmacy",null,null,""]
[null,"Orders",null,""]
[null,null,1,"Are the Pharmacy Orders applications the same across all facilities/pharmacies?",null,null,"Are the Pharmacy Orders applications the same across all facilities/pharmacies?",{"$nulls":4},12,181,"<Data Source>",15]
[null,null,null,""]
[null,null,2,"Are the Pharmacy Orders application version the same across all facilities/pharmacies?",null,null,"Are the Pharmacy Orders application version the same across all facilities/pharmacies?",{"$nulls":4},12,182,"<Data Source>",15]
[null,null,3,"Are the Pharmacy messages encoded orders (verified by the pharmacist)?",null,null,"Are the Pharmacy messages encoded orders (verified by the pharmacist)?",{"$nulls":4},12,183,"<Data Source>",15]
[null,null,null,""]
[null,null,99,"Additional Pharm Orders Notes?",null,null,"Additional Pharm Orders Notes?",{"$nulls":4},12,160,"<Data Source>",15]
["Interface - Radiology",null,null,""]
[null,"Orders",null,""]
[null,null,1,"Are the Radiology Orders applications the same across all facilities?",null,null,"Are the Radiology Orders applications the same across all facilities?",{"$nulls":4},13,184,"<Data Source>",17]
[null,null,null,""]
[null,null,2,"Are the Radiology Orders application versions the same across all facilities?",null,null,"Are the Radiology Orders application versions the same across all facilities?",{"$nulls":4},13,185,"<Data Source>",17]
[null,null,3,"Are the Radiology Orders application interface specifications the same across all facilities?",null,null,"Are the Radiology Orders application interface specifications the same across all facilities?",{"$nulls":4},13,186,"<Data Source>",17]
[null,null,null,""]
[null,null,98,"Additional Radiology Orders Notes?",null,null,"Additional Radiology Orders Notes?",{"$nulls":4},13,152,"<Data Source>",17]
["Interface - Radiology",null,null,""]
[null,"Results",null,""]
[null,null,1,"Are the Radiology Results applications the same across all facilities?",null,null,"Are the Radiology Results applications the same across all facilities?",{"$nulls":4},14,187,"<Data Source>",18]
[null,null,null,""]
[null,null,2,"Are the Radiology Results application versions the same across all facilities?",null,null,"Are the Radiology Results application versions the same across all facilities?",{"$nulls":4},14,188,"<Data Source>",18]
[null,null,3,"Are the Radiology Results application interface specifications the same across all facilities?",null,null,"Are the Radiology Results application interface specifications the same across all facilities?",{"$nulls":4},14,189,"<Data Source>",18]
[null,null,null,""]
[null,null,4,"Are notes sent in NTE segment(s) or via OBX segments(s).  If the latter, is the OBX sub-ID (OBX-4) utilized?",null,null,"Are notes sent in NTE segment(s) or via OBX segments(s).  If the latter, is the OBX sub-ID (OBX-4) utilized?",{"$nulls":4},14,190,"<Data Source>",18]
[null,null,99,"Additional Radiology Results Notes?",null,null,"Additional Radiology Results Notes?",{"$nulls":4},14,153,"<Data Source>",18]
["Network",null,null,""]
[null,"All",null,""]
[null,null,null,""]
[null,null,1,"What kind of Network Infrastructure is in place?",null,null,"What kind of Network Infrastructure is in place?",{"$nulls":4},15,76,"<Data Source>",3]
[null,null,2,"Does the network have Always ON Internet connection?  (Y/N)\n(“Always ON” Internet connection is required for PHIN MS)",null,null,"Does the network have Always ON Internet connection?  (Y/N)\n(“Always ON” Internet connection is required for PHIN MS)",{"$nulls":4},15,77,"<Data Source>",3]
[null,null,null,""]
[null,null,3,"What is the internet bandwidth? \nMinimum 56kbps required, but 384kbps or more is strongly recommended depending on the data transfer volume",null,null,"What is the internet bandwidth? \nMinimum 56kbps required, but 384kbps or more is strongly recommended depending on the data transfer volume",{"$nulls":4},15,78,"<Data Source>",3]
[null,null,4,"What types of security measures are in place to protect data?\n0 Authentication\n0 Access control\n(Only authorized personnel have access to sensitive data)\n0 Audit trails\n(Logs captured to identify attempts to access or modify records)",null,null,"What types of security measures are in place to protect data?\n0 Authentication\n0 Access control\n(Only authorized personnel have access to sensitive data)\n0 Audit trails\n(Logs captured to identify attempts to access or modify records)",{"$nulls":4},15,79,"<Data Source>",3]
[null,null,null,""]
[null,null,5,"Will VPN access to BioSense servers be available?\nFor example, VPN access may be available only during development.",null,null,"Will VPN access to BioSense servers be available?\nFor example, VPN access may be available only during development.",{"$nulls":4},15,82,"<Data Source>",3]
[null,null,6,"Are there documented database or network security guidelines?  If so, please describe.",null,null,"Are there documented database or network security guidelines?  If so, please describe.",{"$nulls":4},15,43,"<Data Source>",3]
[null,null,null,""]
[null,null,7,"Are there timeout constraints currently existing that might impede secure communications with the CDC across the Internet?  For example, the firewall times out after 30 minutes of inactivity.",null,null,"Are there timeout constraints currently existing that might impede secure communications with the CDC across the Internet?  For example, the firewall times out after 30 minutes of inactivity.",{"$nulls":4},15,105,"<Data Source>",3]
[null,null,8,"Do you have a proxy server?  If so, what are the procedures for creating a connection?",null,null,"Do you have a proxy server?  If so, what are the procedures for creating a connection?",{"$nulls":4},15,116,"<Data Source>",3]
[null,null,null,""]
[null,null,9,"Do you have a standard naming convention?  If so what is it?  For production and test? The default naming convention for BioSense servers: BIOSENSExxxxP and BIOSENSExxxxT, where \"xxxx\"  is a sequential number. \"P\" and \"T\" are Production and Text boxes.",null,null,"Do you have a standard naming convention?  If so what is it?  For production and test? The default naming convention for BioSense servers: BIOSENSExxxxP and BIOSENSExxxxT, where \"xxxx\"  is a sequential number. \"P\" and \"T\" are Production and Text boxe","s.",null,null,null,15,143,"<Data Source>",3]
[null,null,99,"Additional Network Notes?",null,null,"Additional Network Notes?",{"$nulls":4},15,83,"<Data Source>",3]
["PHIN",null,null,""]
[null,"All",null,""]
[null,null,null,""]
[null,null,1,"Does the organization have any familiarity with following PHIN Components?\n0 PHIN-MS\n0 Other, please specify",null,null,"Does the organization have any familiarity with following PHIN Components?\n0 PHIN-MS\n0 Other, please specify",{"$nulls":4},16,85,"<Data Source>",4]
[null,null,2,"Who will apply for the Digital Certificate?  What happens if they quit or change jobs?  How will the Digital Certificate information be secured?",null,null,"Who will apply for the Digital Certificate?  What happens if they quit or change jobs?  How will the Digital Certificate information be secured?",{"$nulls":4},16,86,"<Data Source>",4]
[null,null,null,""]
[null,null,99,"Additional PHIN Notes?",null,null,"Additional PHIN Notes?",{"$nulls":4},16,87,"<Data Source>",4]
["Technical",null,null,""]
[null,"Hardware",null,""]
[null,null,1,"Does your environment have any special and/or standard hardware requirements or preferences?  These would include hardware vendor preferences, restrictions, configurations, etc.  Examples would include: Rack mount vs. Tower, Blade vs. other rack mount, IB",null,null,"Does your environment have any special and/or standard hardware requirements or preferences?  These would include hardware vendor preferences, restrictions, configurations, etc.  Examples would include: Rack mount vs. Tower, Blade vs. other rack moun","t, IB",null,null,null,17,90,"<Data Source>",45]
[null,null,null,""]
[null,null,2,"If Rack Mount configuration, what are the rack manufacture, dimensions and available space?",null,null,"If Rack Mount configuration, what are the rack manufacture, dimensions and available space?",{"$nulls":4},17,91,"<Data Source>",45]
[null,null,3,"Are there any UPS slots available and/or would these servers be added to your existing UPS power support? ",null,null,"Are there any UPS slots available and/or would these servers be added to your existing UPS power support? ",{"$nulls":4},17,92,"<Data Source>",45]
[null,null,null,""]
[null,null,4,"Does your environment have sufficient space in the data center (either rack space or floor space) for installing the BioSense hardware?  If not, please explain requirements.",null,null,"Does your environment have sufficient space in the data center (either rack space or floor space) for installing the BioSense hardware?  If not, please explain requirements.",{"$nulls":4},17,96,"<Data Source>",45]
[null,null,5,"Are there deployment environment constraints that may impact the project.  For example, the hardware certification process takes 14 days after it arrives on site.",null,null,"Are there deployment environment constraints that may impact the project.  For example, the hardware certification process takes 14 days after it arrives on site.",{"$nulls":4},17,97,"<Data Source>",45]
[null,null,null,""]
[null,null,6,"Does your data center and/or server share monitors and keyboards across servers?  Will this be the same approach to support the BioSense servers?  ",null,null,"Does your data center and/or server share monitors and keyboards across servers?  Will this be the same approach to support the BioSense servers?  ",{"$nulls":4},17,100,"<Data Source>",45]
[null,null,7,"Is there a cost associated with the physical space for the server in your data center?  ",null,null,"Is there a cost associated with the physical space for the server in your data center?  ",{"$nulls":4},17,101,"<Data Source>",45]
[null,null,null,""]
[null,null,8,"Does your network/hardware group need to apply all the patches for the servers once they get on site or are we able to do so before hand?”",null,null,"Does your network/hardware group need to apply all the patches for the servers once they get on site or are we able to do so before hand?”",{"$nulls":4},17,195,"<Data Source>",45]
[null,null,99,"Additional Technical Hardware Notes?",null,null,"Additional Technical Hardware Notes?",{"$nulls":4},17,161,"<Data Source>",45]
["Technical",null,null,""]
[null,"Software",null,""]
[null,null,null,""]
[null,null,1,"The standard BioSense Data Source Solution is built on a platform using the Windows Server 2003, Standard Edition.  Can your environment support this O/S?  If not, please explain for discussion purposes",null,null,"The standard BioSense Data Source Solution is built on a platform using the Windows Server 2003, Standard Edition.  Can your environment support this O/S?  If not, please explain for discussion purposes",{"$nulls":4},18,88,"<Data Source>",46]
[null,null,2,"The database component of the BioSense Data Source Solution (BioSense Linker) is built using SQL Server 2000 Standard Edition.  Can your environment support this database?  If not, please explain for discussion purposes.",null,null,"The database component of the BioSense Data Source Solution (BioSense Linker) is built using SQL Server 2000 Standard Edition.  Can your environment support this database?  If not, please explain for discussion purposes.",{"$nulls":4},18,89,"<Data Source>",46]
[null,null,null,""]
[null,null,3,"Do you employ any network and/or environment management and/or monitoring utilities?  If so, please identify them (Ex. Tivoli, auto backups, etc).  ",null,null,"Do you employ any network and/or environment management and/or monitoring utilities?  If so, please identify them (Ex. Tivoli, auto backups, etc).  ",{"$nulls":4},18,94,"<Data Source>",46]
[null,null,4,"Does your environment have any experience with the Orion Rhapsody integration product?  ",null,null,"Does your environment have any experience with the Orion Rhapsody integration product?  ",{"$nulls":4},18,95,"<Data Source>",46]
[null,null,null,""]
[null,null,5,"What standard software does the organization load on all of its servers (e.g. backup agents, virus protection, etc)?",null,null,"What standard software does the organization load on all of its servers (e.g. backup agents, virus protection, etc)?",{"$nulls":4},18,118,"<Data Source>",46]
[null,null,98,"Additional Technical Software Notes?",null,null,"Additional Technical Software Notes?",{"$nulls":4},18,162,"<Data Source>",46]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]

{"sheet":"Applications","index":5,"n_rows":44,"n_cols":16,"rows_kept":44,"cut":false,"hidden":false,"merged":[[43,0,43,1]],"flags":["formulas_cached_only"]}
["Data Category","Element Category (copy/paste rows as needed)","Vendor","Application","Application\nVersion","Data\nFormat\n(Ex HL7)","Data\nFormat\nVersion","Via\nInterface?\n(Y/N)","Interface\nEngine","Real\nTime?\n(Y/N)","Test\nEnv?\n(Y/N)","Live?\n(Y/N)","Major\nPlanned\nUpgrade?\n(Y/N)","CLIA (Lab Only)","Close to Sunset Date?à","Comments (note any facilities that deviate from this)"]
[]
["Foundational"]
[null,"Demographic Data (Obscurred)"]
[]
["Foundational"]
[null,"Clinical Data - Visit related"]
[]
["Foundational"]
[null,"Clinical Data - CC"]
[]
["Foundational"]
[null,"Clinical Data - Diagnosis"]
[]
["Foundational"]
[null,"Hospital Census/Utilization"]
[]
["Foundational"]
[null,"General"]
[]
["ED/Clinical"]
[null,"ED/Clinical Data (Emergency Room Data)"]
[]
["Lab/Micro"]
[]
[null,"Lab/Micro Orders"]
[]
["Lab/Micro"]
[null,"Lab/Micro Results"]
[]
["Pharmacy"]
[null,"Medication Orders"]
[]
["Radiology"]
[null,"Radiology Orders"]
[]
["Radiology"]
[null,"Radiology Results"]
[]
["Interface"]
[null,"Engine"]
[]
[]
["àAre any of the applications that will be interfaced to BioSense close to or past their vendor sunset dates?  Are any of the applications unsupported by their original vendors?  If so, how are the applications supported.  This includes the interface engine."]

{"sheet":"Transaction Volumes","index":6,"n_rows":38,"n_cols":9,"rows_kept":38,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Data Category","Element Category (copy/paste rows as needed for different applications)","Venddor and Application","Inpatient?\n(Y/N)","Outpatient?\n(Y/N)","ED?\n(Y/N)","Transaction \nVolume","Frequency (for volume)","Comments (note any facilities that deviate from this)"]
[]
["Foundational"]
[null,"Demographic Data (Obscurred)"]
[]
["Foundational"]
[null,"Clinical Data - Visit related"]
[]
["Foundational"]
[null,"Clinical Data - CC"]
[]
["Foundational"]
[null,"Clinical Data - Diagnosis"]
[]
["Foundational"]
[null,"Hospital Census/Utilization"]
[]
["Foundational"]
[null,"General"]
[]
["ED/Clinical"]
[null,"ED/Clinical Data (Emergency Room Data)"]
[]
["Lab/Micro"]
[]
[null,"Lab/Micro Orders"]
[]
["Lab/Micro"]
[null,"Lab/Micro Results"]
[]
["Pharmacy"]
[null,"Medication Orders"]
[]
["Radiology"]
[null,"Radiology Orders"]
[]
["Radiology"]
[null,"Radiology Results"]

{"sheet":"Messages of Interest","index":7,"n_rows":77,"n_cols":10,"rows_kept":77,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Data Type","Element Type","HL7\nType^Trigger","Description","Data Source\nType^Trigger","Data\nSource\nCaptures?\n(Y/N)","Application\n(Y/N)","Real\nTime?\n(Y/N)","Interface Engine?\n(Y/N)","Comments"]
[]
["Foundational"]
[null,"Demographic Data"]
[null,null,"ADT^A01","Admit/Visit Notification"]
[null,null,"ADT^A02","Transfer a Patient"]
[null,null,"ADT^A03","Discharge/End Visit"]
[null,null,"ADT^A04","Register a Patient"]
[null,null,"ADT^A06","Change an Outpatient to an Inpatient"]
[null,null,"ADT^A07","Change an Inpatient to an Outpatient"]
[null,null,"ADT^A08","Update Patient Information"]
[null,null,"ADT^A11","Cancel Admit / Visit Notification"]
[null,null,"ADT^A12","Cancel Transfer "]
[null,null,"ADT^A13","Cancel Discharge / End Visit"]
[null,null,"ADT^A17","Swap Patients "]
[null,null,"ADT^A18","Merge Patient Information "]
[]
[null,null,"ADT^A28","Add Person or Patient Information"]
[null,null,"ADT^A30","Merge Person Information "]
[null,null,"ADT^A34","Merge Patient Information - Patient ID Only"]
[null,null,"ADT^A35","Merge Patient Information - Account Number Only "]
[null,null,"ADT^A36","Merge Patient Information - Patient ID & Account Number "]
[null,null,"ADT^A39","Merge Person - Patient ID"]
[null,null,"ADT^A40","Merge Patient - Patient Identifier List "]
[null,null,"ADT^A41","Merge Account - Patient Account Number "]
[null,null,"ADT^A43","Move Patient Information - Patient Identifier List  "]
[null,null,"ADT^A44","Move Account Information - Patient Account Number"]
[]
[null,null,"ADT^A45","Move Visit Information - Visit Number "]
[null,null,"ADT^A46","Change Patient ID "]
[null,null,"ADT^A47","Change Patient Identifier List "]
[null,null,"ADT^A49","Change Patient Account Number "]
[null,null,"BAR^P01","Update Diagnosis/Procedure"]
[null,null,"BAR^P12","Update Diagnosis/Procedure"]
["Foundational"]
[null,"Hospital Census/Utilization"]
[null,null,"ORU^R01","Unsolicited Observation Message (Census only)"]
["ED/Clinical"]
[null,"ED/Clinical Data"]
[null,null,"ADT^A08","Update Patient Information"]
[null,null,"ORU^R01","ED/Clinical Observation"]
["Lab/Micro"]
[]
[null,"Lab/Micro Orders"]
[null,null,"OML^O21","Laboratory Order Message"]
[null,null,"OML^O33","Laboratory Order – Multiple Order Per Specimen Message"]
[null,null,"OML^O35","Laboratory Order – Multiple Order Per Container of Specimen Message"]
[null,null,"ORM^O01","General Order Message For Lab"]
["Lab/Micro"]
[null,"Lab/Micro Results"]
[null,null,"ORU^R01","Unsolicited Observation Message - Lab"]
[null,null,"ORU^R30","Unsolicited Point-Of-Care observation message without existing order"]
[null,null,"ORU^R31","Unsolicited new Point-Of-Care observation message"]
[null,null,"OUL^R22","Unsolicited Specimen Oriented Observation Message"]
[]
[null,null,"OUL^R23","Unsolicited Specimen Container Oriented Observation Message"]
[null,null,"OUL^R24","Unsolicited Specimen Container Oriented Observation Message"]
["Pharmacy"]
[null,"Medication Orders"]
[null,null,"OMP^O09","Pharmacy/treatment Order Message"]
[null,null,"ORM^R01","General Order Message For Medication Orders"]
[null,null,"RDE^O01","Pharmacy/Treatment Encoded Order Message"]
[null,null,"RDE^O11","Pharmacy/Treatment Encoded Order Message"]
[null,null,"RDS^O01","Pharmacy/treatment Dispense Message"]
[null,null,"RDS^O13","Pharmacy/treatment Dispense Message"]
["Radiology"]
[null,"Radiology Orders"]
[null,null,"OMI^O23","Imaging Order Message"]
[null,null,"ORM^O01","General Order Message For Rad"]
["Radiology"]
[null,"Radiology Results"]
[null,null,"MDM^T02","Original Document Notification and Content"]
[null,null,"MDM^T04","Document Status Change Notification and Content"]
[null,null,"MDM^T06","Document Addendum Notification and Content"]
[null,null,"MDM^T08","Document Edit Notification and Content"]
[null,null,"MDM^T10","Document Replacement Notification and Content"]
[null,null,"ORU^R01","Unsolicited Observation Message - Rad"]

{"sheet":"Elements of Interest","index":8,"n_rows":595,"n_cols":18,"rows_kept":595,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Data Category","Element Category","Data Element","Description","BioSense HL7 Context","Data Source HL7 Context","DS Message Type(s)","Available?","Application","Comments","Description1","Description2","Description3","Description4","Description5","BS Element Key","Category Key","Data Source"]
["Foundational"]
[null,"Demographic Data"]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},67,20,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.",{"$nulls":4},68,20,"<Data Source>"]
[null,null,"Date of Birth","Patient’s year and month of birth (day is not included for privacy purposes)","PID-7",{"$nulls":5},"Patient’s year and month of birth (day is not included for privacy purposes)",{"$nulls":4},69,20,"<Data Source>"]
[null,null,"Reported Age","Patient’s age as reported in an application at the source.","OBX-5",{"$nulls":5},"Patient’s age as reported in an application at the source.",{"$nulls":4},70,20,"<Data Source>"]
[null,null,"Calculated Age","Patient’s age calculated against admit date/time\nAge = PV1-44 Admit date/time minus PID-7 Date of Birth.\nOnly calculated if both fields are present in the ADT message.\nCannot occur on Merge messages since they do not carry the OBX segment.\nAge greater than or equal to 1 year, units = Years.\nAge less than 1 year and greater than or equal to 1 month, units = Months.\nAge less than 1 month, units = Days.","OBX-5",{"$nulls":5},"Patient’s age calculated against admit date/time\nAge = PV1-44 Admit date/time minus PID-7 Date of Birth.\nOnly calculated if both fields are present in the ADT message.\nCannot occur on Merge messages since they do not carry the OBX segment.\nAge gr","eater than or equal to 1 year, units = Years.\nAge less than 1 year and greater than or equal to 1 month, units = Months.\nAge less than 1 month, units = Days.",null,null,null,71,20,"<Data Source>"]
[null,null,"Sex","Patient sex","PID-8",{"$nulls":5},"Patient sex",{"$nulls":4},72,20,"<Data Source>"]
[null,null,"Zip code","Patient residence 5-digit zip code","PID-11.5",{"$nulls":5},"Patient residence 5-digit zip code",{"$nulls":4},73,20,"<Data Source>"]
[null,null,"State","Patient residence – state","PID-11.4",{"$nulls":5},"Patient residence – state",{"$nulls":4},74,20,"<Data Source>"]
[null,null,"County","Patient residence – county","PID-11.9",{"$nulls":5},"Patient residence – county",{"$nulls":4},75,20,"<Data Source>"]
[null,null,"Country","Patient residence -– country","PID-11.6",{"$nulls":5},"Patient residence -– country",{"$nulls":4},76,20,"<Data Source>"]
[null,null,"Ethnic group","Patient ethnic group (Hispanic or not)","PID-22 ",{"$nulls":5},"Patient ethnic group (Hispanic or not)",{"$nulls":4},77,20,"<Data Source>"]
[null,null,"Race","Patient Race (Multiple patient race codes may be specified)","PID-10",{"$nulls":5},"Patient Race (Multiple patient race codes may be specified)",{"$nulls":4},78,20,"<Data Source>"]
[null,null,"Occupation ","Patient occupation, if collected.  It may be available with the financial information collected for the insured patient.","OBX-5",{"$nulls":5},"Patient occupation, if collected.  It may be available with the financial information collected for the insured patient.",{"$nulls":4},79,20,"<Data Source>"]
[null,null,"Industry ","Industry in which patient works, if collected.","OBX-5",{"$nulls":5},"Industry in which patient works, if collected.",{"$nulls":4},80,20,"<Data Source>"]
[null,null,"Patient Death Indicator","Patient death indicator (Y/N)","PID-30",{"$nulls":5},"Patient death indicator (Y/N)",{"$nulls":4},81,20,"<Data Source>"]
[null,null,"Deceased Date","Patient death date/time, if patient has died","PID-29",{"$nulls":5},"Patient death date/time, if patient has died",{"$nulls":4},82,20,"<Data Source>"]
[null,null,"Last Update Date/Time","Last time demographic data was updated by the source","PID-33",{"$nulls":5},"Last time demographic data was updated by the source",{"$nulls":4},83,20,"<Data Source>"]
[null,null,"Employment Illness-Related Indicator","This field may be used by the source to indicate that is an employment-related encounter.  If this field is populated, pass it forward in the outgoing message.","PV2-15",{"$nulls":5},"This field may be used by the source to indicate that is an employment-related encounter.  If this field is populated, pass it forward in the outgoing message.",{"$nulls":4},65,20,"<Data Source>"]
[null,null,"Identity Unknown Indicator","If this field is populated, it should be passed forward in the outgoing message.","PID-31",{"$nulls":5},"If this field is populated, it should be passed forward in the outgoing message.",{"$nulls":4},84,20,"<Data Source>"]
[null,null,"Admit date/time","Admission or register date/time.","PV1-44",{"$nulls":5},"Admission or register date/time.",{"$nulls":4},51,20,"<Data Source>"]
[null,null,"Discharge date/time","Discharge/sign-out date/time.","PV1-45",{"$nulls":5},"Discharge/sign-out date/time.",{"$nulls":4},52,20,"<Data Source>"]
[null,null,"Chief Complaint","Patient-reported reason for visit when patient is an Emergency  patient.  It may have been entered as text or may make use of drop-down lists to enter canned text.","PV2-3",{"$nulls":5},"Patient-reported reason for visit when patient is an Emergency  patient.  It may have been entered as text or may make use of drop-down lists to enter canned text.",{"$nulls":4},185,20,"<Data Source>"]
[null,null,"Admission Reason","Physician’s reason for admission when patient is an Inpatient.  It may have been entered as text or may make use of drop-down lists to enter canned text.","PV2-3",{"$nulls":5},"Physician’s reason for admission when patient is an Inpatient.  It may have been entered as text or may make use of drop-down lists to enter canned text.",{"$nulls":4},89,20,"<Data Source>"]
[null,null,"Reason for Visit","Reason for outpatient visit when patient is an Outpatient.  It may have been entered as text or may make use of drop-down lists to enter canned text.","PV2-3",{"$nulls":5},"Reason for outpatient visit when patient is an Outpatient.  It may have been entered as text or may make use of drop-down lists to enter canned text.",{"$nulls":4},220,20,"<Data Source>"]
[null,null,"Discharge Diagnosis","Diagnosis or diagnoses entered by a medical records coder based on the physician’s reported diagnosis.   These diagnoses may exist in financial or medical records transactions at the source but they are passed in DG1 segments to CDC.\nIf the date and time each diagnosis was assigned is available, that is also passed.\nIf there are multiple Discharge diagnoses passed, there may be an indication from the source of how they were prioritized, most typically as “Primary” and “Secondary”, which is the Diagnosis Priority element.","DG1-3",{"$nulls":5},"Diagnosis or diagnoses entered by a medical records coder based on the physician’s reported diagnosis.   These diagnoses may exist in financial or medical records transactions at the source but they are passed in DG1 segments to CDC.\nIf the date and"," time each diagnosis was assigned is available, that is also passed.\nIf there are multiple Discharge diagnoses passed, there may be an indication from the source of how they were prioritized, most typically as “Primary” and “Secondary”, which is the"," Diagnosis Priority element.",null,null,187,20,"<Data Source>"]
[null,null,"Discharge Diagnosis Date/Time","Time the Discharge diagnosis was identified","DG1-5",{"$nulls":5},"Time the Discharge diagnosis was identified",{"$nulls":4},249,20,"<Data Source>"]
[null,null,"Discharge Diagnosis priority","Discharge Diagnosis priority","DG1-15",{"$nulls":5},"Discharge Diagnosis priority",{"$nulls":4},234,20,"<Data Source>"]
[null,null,"Discharge Diagnosis type","Discharge Diagnosis type","DG1-6",{"$nulls":5},"Discharge Diagnosis type",{"$nulls":4},248,20,"<Data Source>"]
[null,null,"Working Diagnosis","Clinical impressions assigned as a result of the encounter.  The working diagnosis is the top contender among a list of diagnostic hypotheses.  Often, therapy may be prescribed based on the working diagnosis.; working diagnosis may be revised after additional information is obtained.  \nThe term \"diagnosis\" suggests a greater degree of precision and certainty than a clinical impression, which refers to a preliminary or working diagnosis.  That being said, if information of this nature is available in the source system (and outside of the ED clinical data elements that use the LOINC codes), it is passed in the DG1 segment and marked as the “working” diagnosis type.\nThese working diagnoses may not be available to pass with the foundational clinical elements, but if they are, the DG1 segment is where they are passed, with a Diagnosis Type of “Working”.  If the date and time the diagnosis was assigned are available, that is also passed.\nIf multiple working diagnoses are passed, there may be an indication from the source of how the clinician prioritized them, which is the Diagnosis Priority element.","DG1-3",{"$nulls":5},"Clinical impressions assigned as a result of the encounter.  The working diagnosis is the top contender among a list of diagnostic hypotheses.  Often, therapy may be prescribed based on the working diagnosis.; working diagnosis may be revised after a","dditional information is obtained.  \nThe term \"diagnosis\" suggests a greater degree of precision and certainty than a clinical impression, which refers to a preliminary or working diagnosis.  That being said, if information of this nature is availab","le in the source system (and outside of the ED clinical data elements that use the LOINC codes), it is passed in the DG1 segment and marked as the “working” diagnosis type.\nThese working diagnoses may not be available to pass with the foundational c","linical elements, but if they are, the DG1 segment is where they are passed, with a Diagnosis Type of “Working”.  If the date and time the diagnosis was assigned are available, that is also passed.\nIf multiple working diagnoses are passed, there may"," be an indication from the source of how the clinician prioritized them, which is the Diagnosis Priority element.",221,20,"<Data Source>"]
[null,null,"Working Diagnosis Date/Time","Time the Working diagnosis was identified","DG1-5",{"$nulls":5},"Time the Working diagnosis was identified",{"$nulls":4},250,20,"<Data Source>"]
[null,null,"Working Diagnosis priority","Working Diagnosis priority","DG1-15",{"$nulls":5},"Working Diagnosis priority",{"$nulls":4},235,20,"<Data Source>"]
[null,null,"Working Diagnosis type","Working Diagnosis type","DG1-6",{"$nulls":5},"Working Diagnosis type",{"$nulls":4},237,20,"<Data Source>"]
[null,null,"Admitting Diagnosis","Admitting diagnosis provides more clarity than the Admit Reason field passed in PV2-3.  If the site had admitting diagnoses available to pass with the foundational clinical elements, they are passed in DG1 segments, with a Diagnosis Type of \"Admitting.  If the date and time the diagnosis was assigned is available, that is also passed.","DG1-3",{"$nulls":5},"Admitting diagnosis provides more clarity than the Admit Reason field passed in PV2-3.  If the site had admitting diagnoses available to pass with the foundational clinical elements, they are passed in DG1 segments, with a Diagnosis Type of \"Admittin","g.  If the date and time the diagnosis was assigned is available, that is also passed.",null,null,null,247,20,"<Data Source>"]
[null,null,"Admitting Diagnosis Date/Time","Time the Admitting diagnosis was identified","DG1-5",{"$nulls":5},"Time the Admitting diagnosis was identified",{"$nulls":4},232,20,"<Data Source>"]
[null,null,"Admitting Diagnosis priority","Admitting Diagnosis priority","DG1-15",{"$nulls":5},"Admitting Diagnosis priority",{"$nulls":4},244,20,"<Data Source>"]
[null,null,"Admitting Diagnosis type","Admitting Diagnosis type","DG1-6",{"$nulls":5},"Admitting Diagnosis type",{"$nulls":4},233,20,"<Data Source>"]
[null,null,"Diagnosis At Time Of Discharge","Diagnosis At Time Of Discharge","DG1-3",{"$nulls":5},"Diagnosis At Time Of Discharge",{"$nulls":4},259,20,"<Data Source>"]
[null,null,"Diagnosis At Time Of Discharge Date/Time","Time the Diagnosis At Time Of Discharge was identified","DG1-5",{"$nulls":5},"Time the Diagnosis At Time Of Discharge was identified",{"$nulls":4},260,20,"<Data Source>"]
[null,null,"Diagnosis At Time Of Discharge priority","Diagnosis At Time Of Discharge priority","DG1-15",{"$nulls":5},"Diagnosis At Time Of Discharge priority",{"$nulls":4},261,20,"<Data Source>"]
[null,null,"Diagnosis At Time Of Discharge type","Diagnosis At Time Of Discharge type","DG1-6",{"$nulls":5},"Diagnosis At Time Of Discharge type",{"$nulls":4},262,20,"<Data Source>"]
[null,null,"Discharge Disposition","Discharge Disposition –patient’s anticipated location or status following the visit (admitted, sent home, etc.).","PV1-36",{"$nulls":5},"Discharge Disposition –patient’s anticipated location or status following the visit (admitted, sent home, etc.).",{"$nulls":4},57,20,"<Data Source>"]
[null,null,"Medical Specialty/Hospital Service","Medical Service under which patient is being treated – may be available only for inpatients.","PV1-10",{"$nulls":5},"Medical Service under which patient is being treated – may be available only for inpatients.",{"$nulls":4},58,20,"<Data Source>"]
[null,null,"Patient Class","General type of patient, e.g., Inpatient, Outpatient, Emergency, Recurring, Obstetrics, Preadmit, Commercial Account.  This field may have to be extrapolated from other fields available at the source, such as PV1-18 Patient Type.","PV1-2",{"$nulls":5},"General type of patient, e.g., Inpatient, Outpatient, Emergency, Recurring, Obstetrics, Preadmit, Commercial Account.  This field may have to be extrapolated from other fields available at the source, such as PV1-18 Patient Type.",{"$nulls":4},59,20,"<Data Source>"]
[null,null,"Admission Type ","Circumstances of admission:  Accident, Emergency, Elective, L&D, Newborn, Routine, Urgent (may only be collected on Admitted patient).","PV1-4",{"$nulls":5},"Circumstances of admission:  Accident, Emergency, Elective, L&D, Newborn, Routine, Urgent (may only be collected on Admitted patient).",{"$nulls":4},60,20,"<Data Source>"]
[null,null,"Admission Source","Where the admission originated (ER, Physician, Clinic, HMO, Court, Transfer from SNF, etc.).","PV1-14",{"$nulls":5},"Where the admission originated (ER, Physician, Clinic, HMO, Court, Transfer from SNF, etc.).",{"$nulls":4},254,20,"<Data Source>"]
[null,null,"Point of Care","Local designation of patient location.","PV1-3 ",{"$nulls":5},"Local designation of patient location.",{"$nulls":4},62,20,"<Data Source>"]
[null,null,"Date into Point of Care/location","Date the patient was put into this location.","EVN-2",{"$nulls":5},"Date the patient was put into this location.",{"$nulls":4},63,20,"<Data Source>"]
[null,null,"Admission Level of Care Code","Admission Level of Care may be populated to indicate the level of resources required to care for the patient, e.g., Acute, Chronic, Critical.","PV2-40",{"$nulls":5},"Admission Level of Care may be populated to indicate the level of resources required to care for the patient, e.g., Acute, Chronic, Critical.",{"$nulls":4},64,20,"<Data Source>"]
["Foundational",null,null,""]
[null,"Hospital Census/Utilization",null,""]
[null,null,"Main facility identifier and name","Name and identifier of the parent facility that is a source for one or more data feeds by location.  Either the Main facility identifier or the Satellite facility identifier will be present in MSH-4, but not both.","BHS-4",{"$nulls":5},"Name and identifier of the parent facility that is a source for one or more data feeds by location.  Either the Main facility identifier or the Satellite facility identifier will be present in MSH-4, but not both.",{"$nulls":4},37,21,"<Data Source>"]
[null,null,"Satellite facility identifier and name","One of any number of clinics or locations creating a data feed at a parent facility.  Either the Main facility identifier or the Satellite facility identifier will be present in MSH-4, but not both.","MSH-4",{"$nulls":5},"One of any number of clinics or locations creating a data feed at a parent facility.  Either the Main facility identifier or the Satellite facility identifier will be present in MSH-4, but not both.",{"$nulls":4},38,21,"<Data Source>"]
[null,null,"Name of Report","One report will be used to carry the daily census by unit and the facility summary census data.","OBR-4",{"$nulls":5},"One report will be used to carry the daily census by unit and the facility summary census data.",{"$nulls":4},39,21,"<Data Source>"]
[null,null,"Date/time of report","Date/time of report","OBR-7",{"$nulls":5},"Date/time of report",{"$nulls":4},40,21,"<Data Source>"]
[null,null,"Admissions","Count of overall facility Admissions during the last 24 hours.","OBX-5",{"$nulls":5},"Count of overall facility Admissions during the last 24 hours.",{"$nulls":4},41,21,"<Data Source>"]
[null,null,"Discharges","Count of overall facility Discharges during the last 24 hours.","OBX-5",{"$nulls":5},"Count of overall facility Discharges during the last 24 hours.",{"$nulls":4},42,21,"<Data Source>"]
[null,null,"Deaths","Count of overall facility Deaths during the last 24 hours.","OBX-5",{"$nulls":5},"Count of overall facility Deaths during the last 24 hours.",{"$nulls":4},43,21,"<Data Source>"]
[null,null,"Occupancy","Overall facility occupancy rate if captured on the census report - calculated for the entire facility by dividing the occupied staffed beds by the total staffed beds.  Staffed beds are defined as Adult and Pediatric inpatient beds that are licensed and physically available for which staff is on hand to attend to the patient who occupies the bed. Staffed beds include those occupied and those that are vacant","OBX-5",{"$nulls":5},"Overall facility occupancy rate if captured on the census report - calculated for the entire facility by dividing the occupied staffed beds by the total staffed beds.  Staffed beds are defined as Adult and Pediatric inpatient beds that are licensed a","nd physically available for which staff is on hand to attend to the patient who occupies the bed. Staffed beds include those occupied and those that are vacant",null,null,null,44,21,"<Data Source>"]
[null,null,"Unit","Unit Name","OBX-5",{"$nulls":5},"Unit Name",{"$nulls":4},45,21,"<Data Source>"]
[null,null,"Number of patients","Current number of patients who are occupying a staffed bed for a particular unit.","OBX-5",{"$nulls":5},"Current number of patients who are occupying a staffed bed for a particular unit.",{"$nulls":4},46,21,"<Data Source>"]
[null,null,"Number of beds available","Number of staffed beds for a particular nursing unit that are not occupied and available for use.  Staffed beds are defined as Adult and Pediatric inpatient beds that are licensed and physically available for which staff is on hand to attend to the patient who occupies the bed. Staffed beds include those occupied and those that are vacant.","OBX-5",{"$nulls":5},"Number of staffed beds for a particular nursing unit that are not occupied and available for use.  Staffed beds are defined as Adult and Pediatric inpatient beds that are licensed and physically available for which staff is on hand to attend to the p","atient who occupies the bed. Staffed beds include those occupied and those that are vacant.",null,null,null,47,21,"<Data Source>"]
["ED/Clinical",null,null,""]
[null,"ED/Clinical Data",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},86,22,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.","PID-18 ",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.",{"$nulls":4},87,22,"<Data Source>"]
[null,null,"Date and time of illness onset","Date and time of illness onset -Intended for ED, can be for other patients as well, if this data is available.","OBX-5",{"$nulls":5},"Date and time of illness onset -Intended for ED, can be for other patients as well, if this data is available.",{"$nulls":4},88,22,"<Data Source>"]
[null,null,"ED Problem List","ED Problem List, Differential Diagnosis (the method of consideration of all potential causes of the patient's condition), Signs and Symptoms","OBX-5",{"$nulls":5},"ED Problem List, Differential Diagnosis (the method of consideration of all potential causes of the patient's condition), Signs and Symptoms",{"$nulls":4},223,22,"<Data Source>"]
[null,null,"ED Diagnosis impression","Discharge Diagnosis/Diagnoses made by the Physician","OBX-5",{"$nulls":5},"Discharge Diagnosis/Diagnoses made by the Physician",{"$nulls":4},224,22,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","Chief Complaint Observation pulled from the ED system","OBX-5",{"$nulls":5},"Chief Complaint Observation pulled from the ED system",{"$nulls":4},225,22,"<Data Source>"]
[null,null,"Patient Instructions","References post-care instructions given to the patient, such as “suture care” or “head injury” discharge instructions, if separate from the physician notes.","OBX-5",{"$nulls":5},"References post-care instructions given to the patient, such as “suture care” or “head injury” discharge instructions, if separate from the physician notes.",{"$nulls":4},90,22,"<Data Source>"]
[null,null,"Physician Notes","Encounter notes written by the ED physician to document the visit.","OBX-5",{"$nulls":5},"Encounter notes written by the ED physician to document the visit.",{"$nulls":4},91,22,"<Data Source>"]
[null,null,"Temperature-Date/time of Temperature","ED temperature measurement, including the reference to Celsius or Fahrenheit, and time it was performed.","OBX-5",{"$nulls":5},"ED temperature measurement, including the reference to Celsius or Fahrenheit, and time it was performed.",{"$nulls":4},92,22,"<Data Source>"]
[null,null,"Blood Pressure-BP Date/Time","Systolic/Diastolic blood pressure measurement and the time it was performed","OBX-5",{"$nulls":5},"Systolic/Diastolic blood pressure measurement and the time it was performed",{"$nulls":4},93,22,"<Data Source>"]
[null,null,"Current therapeutic medications","Current therapeutic medications passed as a text string observation.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX ^2.16.840.1.113883.6.1\nOBX-2 Value = TX\nOBX-3 Observation Identifier = 10160-0^ HISTORY OF MEDICATION USE^2.16.840.1.113883.6.1\nOBX-5= Current Therapeutic Medications Text \nOBX-11 = “F”","OBX-5",{"$nulls":5},"Current therapeutic medications passed as a text string observation.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX ^2.16.840.1.113883.6.1\nOBX-2 Value = TX\nOBX-3 Observation Identifier = 10160-0^ HISTORY OF MEDICATION USE^2.16.840.1.113883.6",".1\nOBX-5= Current Therapeutic Medications Text \nOBX-11 = “F”",null,null,null,94,22,"<Data Source>"]
[null,null,"Extended Triage Notes","Provider notes documented in the process of sorting the patient based on need for or likely benefit from immediate medical treatment.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX PT^2.16.840.1.113883.6.1\nOBX-2 Value = TX\nOBX-3 Observation Identifier = 34120-6^INITIAL EVALUATION NOTE^2.16.840.1.113883.6.1\nOBX-5= Extended Triage Notes \nOBX-11 = “F”","OBX-5",{"$nulls":5},"Provider notes documented in the process of sorting the patient based on need for or likely benefit from immediate medical treatment.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX PT^2.16.840.1.113883.6.1\nOBX-2 Value = TX\nOBX-3 Observation ","Identifier = 34120-6^INITIAL EVALUATION NOTE^2.16.840.1.113883.6.1\nOBX-5= Extended Triage Notes \nOBX-11 = “F”",null,null,null,95,22,"<Data Source>"]
[null,null,"ED Acuity","Indicates how quickly care is required, as in “Time to evaluation or treatment not critical”, “Request Prompt Evaluation or Treatment ”, “Request Immediate Evaluation or Treatment”.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX PT^2.16.840.1.113883.6.1\nOBX-2 Value = CE\nOBX-3 Observation Identifier = 11283-9^ ACUITY ASSESSMENT^ 2.16.840.1.113883.6.1\nOBX-5= ^^^LocalAcuityCode^LocalDescription^LocalCoding System\nOBX-11 = “F”","OBX-5",{"$nulls":5},"Indicates how quickly care is required, as in “Time to evaluation or treatment not critical”, “Request Prompt Evaluation or Treatment ”, “Request Immediate Evaluation or Treatment”.  OBR-4 18698-1^ED CLINICAL FINDING INFORMATION COMPLX PT^2.16.840.1.","113883.6.1\nOBX-2 Value = CE\nOBX-3 Observation Identifier = 11283-9^ ACUITY ASSESSMENT^ 2.16.840.1.113883.6.1\nOBX-5= ^^^LocalAcuityCode^LocalDescription^LocalCoding System\nOBX-11 = “F”",null,null,null,96,22,"<Data Source>"]
[null,null,"Procedures performed","Any test or procedure codes entered as a result of the encounter","OBR-44 or OBR-31",{"$nulls":5},"Any test or procedure codes entered as a result of the encounter",{"$nulls":4},263,22,"<Data Source>"]
["Lab/Micro",null,null,""]
[null,"Lab/Micro Orders",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},158,26,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ",{"$nulls":4},159,26,"<Data Source>"]
[null,null,"Order Number","Tracking number created when the order is placed","OBR-2",{"$nulls":5},"Tracking number created when the order is placed",{"$nulls":4},160,26,"<Data Source>"]
[null,null,"Test Code/Name","Test code /test description","OBR-4",{"$nulls":5},"Test code /test description",{"$nulls":4},161,26,"<Data Source>"]
[null,null,"Relevant Clinical Information","Relevant Clinical Information","OBR-13",{"$nulls":5},"Relevant Clinical Information",{"$nulls":4},226,26,"<Data Source>"]
[null,null,"Reason for Test","Reasons for testing sent with order information.  This field can repeat.","OBR-31",{"$nulls":5},"Reasons for testing sent with order information.  This field can repeat.",{"$nulls":4},164,26,"<Data Source>"]
[null,null,"Specimen Type","Specimen type or source, if entered at the time of order entry.","OBR-15.1",{"$nulls":5},"Specimen type or source, if entered at the time of order entry.",{"$nulls":4},227,26,"<Data Source>"]
[null,null,"Order Date/time","Date/time service was ordered in the system","OBR-6",{"$nulls":5},"Date/time service was ordered in the system",{"$nulls":4},162,26,"<Data Source>"]
[null,null,"Begin Date/time","Date/time service is requested to occur","ORC-15",{"$nulls":5},"Date/time service is requested to occur",{"$nulls":4},183,26,"<Data Source>"]
["Lab/Micro",null,null,""]
[null,"Lab/Micro Results",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},102,27,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ",{"$nulls":4},103,27,"<Data Source>"]
[null,null,"Reporting laboratory ","Reporting laboratory identifier and name","MSH-3",{"$nulls":5},"Reporting laboratory identifier and name",{"$nulls":4},104,27,"<Data Source>"]
[null,null,"Diagnostic Service Section ID","Identifies the department that performed the service.","OBR-24",{"$nulls":5},"Identifies the department that performed the service.",{"$nulls":4},105,27,"<Data Source>"]
[null,null,"Performing laboratory","Performing laboratory id and name (may be different for referral lab testing)","OBX-15",{"$nulls":5},"Performing laboratory id and name (may be different for referral lab testing)",{"$nulls":4},106,27,"<Data Source>"]
[null,null,"Result Status","Status of the report (preliminary, final, corrected). This field is required in a result message, and is typically used where the level of detail does not need to be at the individual observation level (OBX-11).  This element was added to support the Radi","OBR-25",{"$nulls":5},"Status of the report (preliminary, final, corrected). This field is required in a result message, and is typically used where the level of detail does not need to be at the individual observation level (OBX-11).  This element was added to support the"," Radi",null,null,null,107,27,"<Data Source>"]
[null,null,"Report date/time","Report Date – applies to entire message as a report, not to individual results","OBR-22",{"$nulls":5},"Report Date – applies to entire message as a report, not to individual results",{"$nulls":4},108,27,"<Data Source>"]
[null,null,"Collection date","Sample collection date","OBR-7",{"$nulls":5},"Sample collection date",{"$nulls":4},109,27,"<Data Source>"]
[null,null,"Collection method","Specimen collection method, e.g. (swab, bronchoscopy, phlebotomy), if present in the result message","OBR-15.3",{"$nulls":5},"Specimen collection method, e.g. (swab, bronchoscopy, phlebotomy), if present in the result message",{"$nulls":4},110,27,"<Data Source>"]
[null,null,"Specimen site","Specimen source site (body site where specimen collected)","OBR-15.4",{"$nulls":5},"Specimen source site (body site where specimen collected)",{"$nulls":4},111,27,"<Data Source>"]
[null,null,"Specimen type","Specimen (what is collected?)","OBR-15.1",{"$nulls":5},"Specimen (what is collected?)",{"$nulls":4},112,27,"<Data Source>"]
[null,null,"Point of Care","Location of patient when specimen was drawn, if available","PV1-3",{"$nulls":5},"Location of patient when specimen was drawn, if available",{"$nulls":4},113,27,"<Data Source>"]
[null,null,"Accession date","Accession date (date received by lab)","OBR-14",{"$nulls":5},"Accession date (date received by lab)",{"$nulls":4},114,27,"<Data Source>"]
[null,null,"Accession ID","Accession number assigned by laboratory","SPM-2.2",{"$nulls":5},"Accession number assigned by laboratory",{"$nulls":4},115,27,"<Data Source>"]
[null,null,"Filler Order Number","Tracking number assigned by laboratory","OBR-3",{"$nulls":5},"Tracking number assigned by laboratory",{"$nulls":4},116,27,"<Data Source>"]
[null,null,"Sequence number","Reported sequence of result.  (Micro) sequence of organism from isolate","OBX-1",{"$nulls":5},"Reported sequence of result.  (Micro) sequence of organism from isolate",{"$nulls":4},117,27,"<Data Source>"]
[null,null,"Ordered Test Code/Name","Ordered test code/description; includes susceptibility panel at this level","OBR-4",{"$nulls":5},"Ordered test code/description; includes susceptibility panel at this level",{"$nulls":4},118,27,"<Data Source>"]
[null,null,"Resulted Test Code/Name","Test code/description as known by the laboratory; identifies individual drugs tested at this level","OBX-3",{"$nulls":5},"Test code/description as known by the laboratory; identifies individual drugs tested at this level",{"$nulls":4},119,27,"<Data Source>"]
[null,null,"Organism identified","Organism code/description when result is an organism","OBX-5",{"$nulls":5},"Organism code/description when result is an organism",{"$nulls":4},120,27,"<Data Source>"]
[null,null,"Method type ","Methodology of test","OBX-17",{"$nulls":5},"Methodology of test",{"$nulls":4},121,27,"<Data Source>"]
[null,null,"Result other than organism","Result depends on type of test being done – may be numeric results or coded entry","OBX-5",{"$nulls":5},"Result depends on type of test being done – may be numeric results or coded entry",{"$nulls":4},122,27,"<Data Source>"]
[null,null,"Result unit","Units of result (this is needed for numeric results)","OBX-6",{"$nulls":5},"Units of result (this is needed for numeric results)",{"$nulls":4},123,27,"<Data Source>"]
[null,null,"Test interpretation","Lab interpretation (non-micro) – “Abnormal”, “High.”","OBX-8",{"$nulls":5},"Lab interpretation (non-micro) – “Abnormal”, “High.”",{"$nulls":4},124,27,"<Data Source>"]
[null,null,"Susceptibility test interpretation","Lab interpretation (micro) – “Sensitive”, “Resistant”, “Indeterminate.”","OBX-8",{"$nulls":5},"Lab interpretation (micro) – “Sensitive”, “Resistant”, “Indeterminate.”",{"$nulls":4},125,27,"<Data Source>"]
[null,null,"Test status","Status of susceptibility testing (individual test status such as prelim, final, corrected)","OBX-11",{"$nulls":5},"Status of susceptibility testing (individual test status such as prelim, final, corrected)",{"$nulls":4},126,27,"<Data Source>"]
[null,null,"Result notes ","Notes and comments that the laboratory sends to clarify results","NTE-3",{"$nulls":5},"Notes and comments that the laboratory sends to clarify results",{"$nulls":4},127,27,"<Data Source>"]
[null,null,"References Range","Normal range values for numeric testing.","OBX-7",{"$nulls":5},"Normal range values for numeric testing.",{"$nulls":4},128,27,"<Data Source>"]
["Pharmacy",null,null,""]
[null,"Medication Orders",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},130,31,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ",{"$nulls":4},131,31,"<Data Source>"]
[null,null,"Order Number","Tracking number created when the order is placed","ORC-2",{"$nulls":5},"Tracking number created when the order is placed",{"$nulls":4},132,31,"<Data Source>"]
[null,null,"Order Date/time","Date/time medications were ordered","ORC-9",{"$nulls":5},"Date/time medications were ordered",{"$nulls":4},133,31,"<Data Source>"]
[null,null,"Begin date/time","Date/time medications should start being administered","ORC-15",{"$nulls":5},"Date/time medications should start being administered",{"$nulls":4},134,31,"<Data Source>"]
[null,null,"Drug code/name","Name and code representation of drug ordered","RXO-1",{"$nulls":5},"Name and code representation of drug ordered",{"$nulls":4},135,31,"<Data Source>"]
[null,null,"Drug Strength – Requested Give Strength","Ordered drug strength (may be part of drug name in some formularies) – this field is required when RXO-1 Requested Give Code does not specify the strength.  The numeric part of the strength is RXO-18 and the units are RXO-19.    (may also need RXO-25 and Requested Drug Strength Volume and RXO-26 Requested Drug Strength Volume Units when a drug strength is expressed as a concentration)","RXO-18",{"$nulls":5},"Ordered drug strength (may be part of drug name in some formularies) – this field is required when RXO-1 Requested Give Code does not specify the strength.  The numeric part of the strength is RXO-18 and the units are RXO-19.    (may also need RXO-25"," and Requested Drug Strength Volume and RXO-26 Requested Drug Strength Volume Units when a drug strength is expressed as a concentration)",null,null,null,136,31,"<Data Source>"]
[null,null,"Drug Strength – Requested Give Units","Ordered drug strength (may be part of drug name in some formularies) – this field is required when RXO-1 Requested Give Code does not specify the strength.  The numeric part of the strength is RXO-18 and the units are RXO-19.","RXO-19",{"$nulls":5},"Ordered drug strength (may be part of drug name in some formularies) – this field is required when RXO-1 Requested Give Code does not specify the strength.  The numeric part of the strength is RXO-18 and the units are RXO-19.",{"$nulls":4},230,31,"<Data Source>"]
[null,null,"Drug Strength - Requested Volume","Requested Drug Strength Volume","RXO-25",{"$nulls":5},"Requested Drug Strength Volume",{"$nulls":4},256,31,"<Data Source>"]
[null,null,"Drug Strength - Requested Volume Units","Requested Drug Strength Volume Units when a drug strength is expressed as a concentration.","RXO-26",{"$nulls":5},"Requested Drug Strength Volume Units when a drug strength is expressed as a concentration.",{"$nulls":4},257,31,"<Data Source>"]
[null,null,"Dosage - Requested Give Amount Minimum for variable dose order","The ordered amount of the drug (min for variable dose)","RXO-2",{"$nulls":5},"The ordered amount of the drug (min for variable dose)",{"$nulls":4},137,31,"<Data Source>"]
[null,null,"Dosage - Requested Give Amount Maximum for variable dose order","The ordered amount of the drug (max for variable dose)","RXO-3",{"$nulls":5},"The ordered amount of the drug (max for variable dose)",{"$nulls":4},231,31,"<Data Source>"]
[null,null,"Dosage - Requested Give Units","The ordered amount of the drug - units","RXO-4",{"$nulls":5},"The ordered amount of the drug - units",{"$nulls":4},229,31,"<Data Source>"]
[null,null,"Form","Form in which the drug is to be dispensed, as in Tablet, Capsule, Spray, IV preparation","RXO-5",{"$nulls":5},"Form in which the drug is to be dispensed, as in Tablet, Capsule, Spray, IV preparation",{"$nulls":4},138,31,"<Data Source>"]
[null,null,"Frequency","How many times per day the drug should be administered/taken","ORC-7.2.1",{"$nulls":5},"How many times per day the drug should be administered/taken",{"$nulls":4},140,31,"<Data Source>"]
[null,null,"Duration","How long the prescription lasts-may have a “number to dispense” or a “stop date” or a duration, depending on the system","RXO-11",{"$nulls":5},"How long the prescription lasts-may have a “number to dispense” or a “stop date” or a duration, depending on the system",{"$nulls":4},141,31,"<Data Source>"]
[null,null,"Pharmacy Order Type","If this optional field is populated, it may be used to filter medication orders from other types of Pharmacy orders, such as IV preparations.  A default value of \"M\" is assumed.","RXO-27",{"$nulls":5},"If this optional field is populated, it may be used to filter medication orders from other types of Pharmacy orders, such as IV preparations.  A default value of \"M\" is assumed.",{"$nulls":4},142,31,"<Data Source>"]
[null,null,"Total Daily Dose","This field contains the total daily dose for this particular pharmaceutical as expressed in terms of actual dispense units, e.g., Cipro 1000 mg/day.  Other data elements have broken it up into dose per frequency.","RXO-23",{"$nulls":5},"This field contains the total daily dose for this particular pharmaceutical as expressed in terms of actual dispense units, e.g., Cipro 1000 mg/day.  Other data elements have broken it up into dose per frequency.",{"$nulls":4},143,31,"<Data Source>"]
[null,null,"Route","Ordered route of administration, e.g., P.O, intranasal, IV","RXR-1",{"$nulls":5},"Ordered route of administration, e.g., P.O, intranasal, IV",{"$nulls":4},139,31,"<Data Source>"]
["Radiology",null,null,""]
[null,"Radiology Orders",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},170,29,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility. ",{"$nulls":4},179,29,"<Data Source>"]
[null,null,"Order Number","Tracking number created when the order is placed","OBR-2",{"$nulls":5},"Tracking number created when the order is placed",{"$nulls":4},180,29,"<Data Source>"]
[null,null,"Test Code/Name","Test code /test description","OBR-4",{"$nulls":5},"Test code /test description",{"$nulls":4},181,29,"<Data Source>"]
[null,null,"Relevant Clinical Information","Relevant Clinical Information","OBR-13",{"$nulls":5},"Relevant Clinical Information",{"$nulls":4},228,29,"<Data Source>"]
[null,null,"Reason for Test","Reasons for testing sent with order information.  This field can repeat.","OBR-31",{"$nulls":5},"Reasons for testing sent with order information.  This field can repeat.",{"$nulls":4},184,29,"<Data Source>"]
[null,null,"Order Date/time","Date/time service was ordered in the system","OBR-6",{"$nulls":5},"Date/time service was ordered in the system",{"$nulls":4},182,29,"<Data Source>"]
[null,null,"Begin Date/time","Date/time service is requested to occur","ORC-15",{"$nulls":5},"Date/time service is requested to occur",{"$nulls":4},163,29,"<Data Source>"]
["Radiology",null,null,""]
[null,"Radiology Results",null,""]
[null,null,"BioSense Patient ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.","PID-3",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to a patient’s medical record within the healthcare facility.",{"$nulls":4},145,30,"<Data Source>"]
[null,null,"BioSense Visit ID","Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.","PID-18",{"$nulls":5},"Unique identifier created by the BioSense integrator application to allow the healthcare facility to track non-identified BioSense data back to the corresponding visit record or records within the facility.",{"$nulls":4},146,30,"<Data Source>"]
[null,null,"Report date/time","Report/Reading Date ","OBR-22",{"$nulls":5},"Report/Reading Date ",{"$nulls":4},147,30,"<Data Source>"]
[null,null,"Result Status","Status of the report (preliminary, final, corrected). This field is required in a result message, and is typically used where the level of detail does not need to be at the individual observation level (OBX-11).  This element was added to support the Radiology and the Laboratory reports.","OBR-25",{"$nulls":5},"Status of the report (preliminary, final, corrected). This field is required in a result message, and is typically used where the level of detail does not need to be at the individual observation level (OBX-11).  This element was added to support the"," Radiology and the Laboratory reports.",null,null,null,148,30,"<Data Source>"]
[null,null,"Diagnostic Service Section ID","Identifies the type of department that is performing the service. If this element is populated, it could be used to group types of tests, e.g., “Radiology”, “Nuclear Medicine”, “CT”","OBR-24",{"$nulls":5},"Identifies the type of department that is performing the service. If this element is populated, it could be used to group types of tests, e.g., “Radiology”, “Nuclear Medicine”, “CT”",{"$nulls":4},149,30,"<Data Source>"]
[null,null,"Procedure date","Date the exam was performed","OBR-7",{"$nulls":5},"Date the exam was performed",{"$nulls":4},150,30,"<Data Source>"]
[null,null,"Radiology Number","Tracking number assigned by radiology","OBR-3",{"$nulls":5},"Tracking number assigned by radiology",{"$nulls":4},151,30,"<Data Source>"]
[null,null,"Test Performed","Performed test code/description","OBR-4",{"$nulls":5},"Performed test code/description",{"$nulls":4},152,30,"<Data Source>"]
[null,null,"Site/testing description","Radiologist’s description of test performed and body site  (possibly with code suffix “ANT”)","OBX-5",{"$nulls":5},"Radiologist’s description of test performed and body site  (possibly with code suffix “ANT”)",{"$nulls":4},153,30,"<Data Source>"]
[null,null,"Impressions","Radiologist’s diagnosis and impressions.  OBX-2=TX\nOBX-3 19005-8^ X-RAY IMPRESSION^LN\nOBX-5=Impressions text (the entire report may use this LOINC if unable to break it down more discretely)","OBX-5",{"$nulls":5},"Radiologist’s diagnosis and impressions.  OBX-2=TX\nOBX-3 19005-8^ X-RAY IMPRESSION^LN\nOBX-5=Impressions text (the entire report may use this LOINC if unable to break it down more discretely)",{"$nulls":4},154,30,"<Data Source>"]
[null,null,"Recommendations","Radiologist’s recommendations.   OBX-2=TX\nOBX-3 18783-1^ RADIOLOGY STUDY RECOMMENDATION^LN\nOBX-5=Recommendations text (if able to break it down discretely)","OBX-5",{"$nulls":5},"Radiologist’s recommendations.   OBX-2=TX\nOBX-3 18783-1^ RADIOLOGY STUDY RECOMMENDATION^LN\nOBX-5=Recommendations text (if able to break it down discretely)",{"$nulls":4},155,30,"<Data Source>"]
[null,null,"Procedures","Procedure codes passed with the result, if available","OBR-44",{"$nulls":5},"Procedure codes passed with the result, if available",{"$nulls":4},156,30,"<Data Source>"]
["Foundational",null,null,""]
[null,"Additional Elements Needed for Communications and Processing",null,""]
[null,null,"Field Separator","The character to be used as the field separator for the rest of the message.  The supported value is |, ASCII (124). (Required for Messaging)","MSH-1",{"$nulls":5},"The character to be used as the field separator for the rest of the message.  The supported value is |, ASCII (124). (Required for Messaging)",{"$nulls":4},1,19,"<Data Source>"]
[null,null,"Encoding Characters","The four characters that always appear in the same order in this field are: |^~\\&|  (Required for Messaging)","MSH-2",{"$nulls":5},"The four characters that always appear in the same order in this field are: |^~\\&|  (Required for Messaging)",{"$nulls":4},2,19,"<Data Source>"]
[null,null,"Sending Facility","This field uniquely identifies the facility that created the source message. ","MSH-4",{"$nulls":5},"This field uniquely identifies the facility that created the source message. ",{"$nulls":4},3,19,"<Data Source>"]
[null,null,"Receiving Application","This field contains the OID for BioSense for all messages.","MSH-5",{"$nulls":5},"This field contains the OID for BioSense for all messages.",{"$nulls":4},4,19,"<Data Source>"]
[null,null,"Receiving Facility","This field contains the OID for CDC PHIN for all messages.","MSH-6",{"$nulls":5},"This field contains the OID for CDC PHIN for all messages.",{"$nulls":4},5,19,"<Data Source>"]
[null,null,"Date/Time Of Message","This field contains the date/time the message was created by the sending system. (Required for Messaging)","MSH-7",{"$nulls":5},"This field contains the date/time the message was created by the sending system. (Required for Messaging)",{"$nulls":4},6,19,"<Data Source>"]
[null,null,"Message Type","This field contains the message type, trigger event, and the message structure ID for the message. (Required for Messaging)","MSH-9",{"$nulls":5},"This field contains the message type, trigger event, and the message structure ID for the message. (Required for Messaging)",{"$nulls":4},7,19,"<Data Source>"]
[null,null,"Message Control ID","This field contains a source identifier plus timestamp plus counter that uniquely identifies the message instance from the sending application.  (Required for Messaging)","MSH-10",{"$nulls":5},"This field contains a source identifier plus timestamp plus counter that uniquely identifies the message instance from the sending application.  (Required for Messaging)",{"$nulls":4},8,19,"<Data Source>"]
[null,null,"Processing ID","This field is used to indicate the intent for processing the message (Required for Messaging)","MSH-11",{"$nulls":5},"This field is used to indicate the intent for processing the message (Required for Messaging)",{"$nulls":4},9,19,"<Data Source>"]
[null,null,"Version ID","This field contains the HL7 version number. (Required for Messaging)","MSH-12",{"$nulls":5},"This field contains the HL7 version number. (Required for Messaging)",{"$nulls":4},10,19,"<Data Source>"]
[null,null,"Message Conformance ID","Version of the PHIN Messaging Guide to which the message conforms.","MSH-21",{"$nulls":5},"Version of the PHIN Messaging Guide to which the message conforms.",{"$nulls":4},275,19,"<Data Source>"]
[null,null,"Event Type Code","This field should carry the same code as MSH-9 component 2, event type. (Required for ADT messages)","EVN-1",{"$nulls":5},"This field should carry the same code as MSH-9 component 2, event type. (Required for ADT messages)",{"$nulls":4},12,19,"<Data Source>"]
[null,null,"Recorded Date/Time","Generally this is the time the transaction was created from the original ADT message. (Required for ADT messages)","EVN-2",{"$nulls":5},"Generally this is the time the transaction was created from the original ADT message. (Required for ADT messages)",{"$nulls":4},13,19,"<Data Source>"]
[null,null,"Set ID - PID","|1| (only one patient/one PID segment per message is supported)","PID-1",{"$nulls":5},"|1| (only one patient/one PID segment per message is supported)",{"$nulls":4},14,19,"<Data Source>"]
[null,null,"Patient Name","This is a required field for the PID segment.  The field will contain “” for de-identification purposes. (Required field)","PID-5",{"$nulls":5},"This is a required field for the PID segment.  The field will contain “” for de-identification purposes. (Required field)",{"$nulls":4},15,19,"<Data Source>"]
[null,null,"County Code","This field will be used to pass the original County code, if there is a discrepancy created by normalization of the county codes at the source.","PID-12",{"$nulls":5},"This field will be used to pass the original County code, if there is a discrepancy created by normalization of the county codes at the source.",{"$nulls":4},16,19,"<Data Source>"]
[null,null,"Set ID - PV1","Only one PV1 segment will occur per message.  This field will contain the value “1.”","PV1-1",{"$nulls":5},"Only one PV1 segment will occur per message.  This field will contain the value “1.”",{"$nulls":4},17,19,"<Data Source>"]
[null,null,"Servicing Facility","May be used to carry the OID for the physical facility of care .","PV1-39",{"$nulls":5},"May be used to carry the OID for the physical facility of care .",{"$nulls":4},277,19,"<Data Source>"]
[null,null,"Clinic Organization Name","This field may contain information used to identify the particular organization or clinic where the data was collected.","PV2-23",{"$nulls":5},"This field may contain information used to identify the particular organization or clinic where the data was collected.",{"$nulls":4},18,19,"<Data Source>"]
[null,null,"Set ID – DG1","This field contains a digit that identifies the instance of the segment. For the first occurrence of the segment the sequence number is |1|, for the second occurrence it is |2| , etc.","DG1-1",{"$nulls":5},"This field contains a digit that identifies the instance of the segment. For the first occurrence of the segment the sequence number is |1|, for the second occurrence it is |2| , etc.",{"$nulls":4},19,19,"<Data Source>"]
[null,null,"Set ID - PR1","This field contains the sequence number for this transaction.","PR1-1",{"$nulls":5},"This field contains the sequence number for this transaction.",{"$nulls":4},20,19,"<Data Source>"]
[null,null,"Observation Sub-ID","This field is used to distinguish between multiple OBX segments with the same observation ID organized under one OBR.  Thus, the Sub-ID allows related OBX segments to be linked.   ","OBX-4",{"$nulls":5},"This field is used to distinguish between multiple OBX segments with the same observation ID organized under one OBR.  Thus, the Sub-ID allows related OBX segments to be linked.   ",{"$nulls":4},21,19,"<Data Source>"]
[null,null,"Order Control Code","Code used by HL7 Order messages to determine the function of the order segment.  This field may be considered the \"trigger event\" identifier for orders.  It is a required field when the ORC is used.","ORC-1",{"$nulls":5},"Code used by HL7 Order messages to determine the function of the order segment.  This field may be considered the \"trigger event\" identifier for orders.  It is a required field when the ORC is used.",{"$nulls":4},22,19,"<Data Source>"]
[null,null,"Placer Order Number","The placer order number field may contain a unique identifier that was created by the ordering application. (populated in Order messages)","ORC-2",{"$nulls":5},"The placer order number field may contain a unique identifier that was created by the ordering application. (populated in Order messages)",{"$nulls":4},23,19,"<Data Source>"]
[null,null,"Filler Order Number","The filler order number field contains a unique identifier created by the fulfiller of the order. (populated in Result messages)","ORC-3",{"$nulls":5},"The filler order number field contains a unique identifier created by the fulfiller of the order. (populated in Result messages)",{"$nulls":4},24,19,"<Data Source>"]
[null,null,"Date/Time of Transaction","Time when service was requested in the system. (populated in Order messages)","ORC-9",{"$nulls":5},"Time when service was requested in the system. (populated in Order messages)",{"$nulls":4},25,19,"<Data Source>"]
[null,null,"Set ID-OBR","Sequence number of OBR instances (populated in Result messages)","OBR-1",{"$nulls":5},"Sequence number of OBR instances (populated in Result messages)",{"$nulls":4},26,19,"<Data Source>"]
[null,null,"Observation End Date/Time","This field may contain a stop time for the observation.","OBR-8",{"$nulls":5},"This field may contain a stop time for the observation.",{"$nulls":4},27,19,"<Data Source>"]
[null,null,"Parent","Used to link reflex tests back to a parent order.  This field links susceptibility panel orders back to the parent culture order.","OBR-29",{"$nulls":5},"Used to link reflex tests back to a parent order.  This field links susceptibility panel orders back to the parent culture order.",{"$nulls":4},29,19,"<Data Source>"]
[null,null,"Parent Result","Field used to link reflex tests back to result previously reported.  It ties a susceptibility panel back to the organism for which it was run.","OBR-26",{"$nulls":5},"Field used to link reflex tests back to result previously reported.  It ties a susceptibility panel back to the organism for which it was run.",{"$nulls":4},276,19,"<Data Source>"]
[null,null,"Set ID - NTE","Sequence number used to maintain order of comments (microbiology results)","NTE-1",{"$nulls":5},"Sequence number used to maintain order of comments (microbiology results)",{"$nulls":4},30,19,"<Data Source>"]
[null,null,"Set ID – SPM","Segment sequence number (microbiology results)","SPM-1",{"$nulls":5},"Segment sequence number (microbiology results)",{"$nulls":4},31,19,"<Data Source>"]
[null,null,"Specimen Type - SPM","The specimen type remains in the OBR-15 legacy location.  If the SPM segment is used to convey the accession number, this required field will contain “”.  OBR-15 is the only place that a specimen type is sent","SPM-4",{"$nulls":5},"The specimen type remains in the OBR-15 legacy location.  If the SPM segment is used to convey the accession number, this required field will contain “”.  OBR-15 is the only place that a specimen type is sent",{"$nulls":4},32,19,"<Data Source>"]
[null,null,"Provider's Pharmacy/Treatment Instructions","The conditional note on RXO-1 indicates if there is a free text order (i.e., the drug is not coded), then RXO-6 may contain a description of the ordered drug.   It is preferable to receive the drug code and description in RXO-1. (RXO-6 included only for free-text drug orders)","RXO-6",{"$nulls":5},"The conditional note on RXO-1 indicates if there is a free text order (i.e., the drug is not coded), then RXO-6 may contain a description of the ordered drug.   It is preferable to receive the drug code and description in RXO-1. (RXO-6 included only ","for free-text drug orders)",null,null,null,33,19,"<Data Source>"]
[null,null,"Prior Patient Identifier List","This field will contain the BioSense identifier only.  This field is used only when there has been a merge transaction at the source which requires the BioSense Patient or Visit ID to change","MRG-1",{"$nulls":5},"This field will contain the BioSense identifier only.  This field is used only when there has been a merge transaction at the source which requires the BioSense Patient or Visit ID to change",{"$nulls":4},34,19,"<Data Source>"]
[null,null,"Prior Patient Account Number","This field will contain a BioSense Visit ID and is used only when there has been a merge transaction at the source which requires the BioSense Visit ID to change","MRG-3",{"$nulls":5},"This field will contain a BioSense Visit ID and is used only when there has been a merge transaction at the source which requires the BioSense Visit ID to change",{"$nulls":4},35,19,"<Data Source>"]
[null,null,null,""]
["MDS Elements that are not BioSense Elements"]
["ED/Clinical","ED/Clinical Data","Pulse Oximetry ","Record pulse oximetry value during triage. \nPassed as observation tagged with LOINC code: ‘19960-4^PULSE OXIMETRY^LN’ \nincluding timestamp for when it was done "]
["ED/Clinical","ED/Clinical Data","Provider Identifier ","Unique facility-specific provider identifier \nProposed definition: “Unique provider (clinician) identifier. This data element is assumed to meet local biosurveillance needs.” \nNeed clarification from AHIC regarding provider role(s): (e.g., attending, primary). "]
["Lab","Orders","Provider Identifier ","Unique facility-specific provider identifier \nProposed definition: “Unique provider (clinician) identifier. This data element is assumed to meet local biosurveillance needs.” \nNeed clarification from AHIC regarding provider role(s): (e.g., attending, primary). "]
["Lab","Results","Ordering Provider Identifier ","Provider of record for the test result that is being reported. "]
["Foundational","Hospital Census/Utilization","Facility Name ","Name of facility \n“Organization Name” in HAVE document "]
["Foundational","Hospital Census/Utilization","Facility Location ","City and State [May use FIPS county codes] \n“Organization Location” in HAVE document \nCity and State are Coded data type. "]
["Foundational","Hospital Census/Utilization","Number of Facility Beds ","All facility beds regardless of licensing status. "]
["Foundational","Hospital Census/Utilization","Number of Licensed Beds ","All facility beds considered licensed in that jurisdiction. "]
["Foundational","Hospital Census/Utilization","Clinical Status","Facility’s clinical resources are operating: \nNormal: Within normal limits \nLevel-1: At Level-1 surge conditions. \nLevel-2: At Level-2 surge conditions. \nFull: Exceeded; acceptable care cannot be provided to additional patients. Diversion or community surge response is required.\nPassed as observation with OASIS/HAVE XML tag: ‘ClinicalStatus’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","Facility Status ","Facility resources are operating under: \nNormal - No conditions exist that adversely affect the general operations of the facility. \nCompromised - General operations of the facility have been affected due to damage, operating on emergency backup systems, or facility contamination. \nEvacuating - Indicates that a hospital is in the process of a partial or full evacuation. \nClosed – Closure; facility no longer capable of providing services and only emergency services/restoration personnel may remain in the facility. \nPassed as observation with OASIS/HAVE XML tag: ‘HospitalFacilityStatus’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","Facility Operations ","Status of supplies necessary for facility operations. \nAdequate - Meets the current needs. \nInsufficient – Current needs are not being met. \nPassed as observation with OASIS/HAVE XML tag: ‘FacilityOperations’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","Staffing ","Available personnel to support facility operations. \nAdequate - Meets the current needs. \nInsufficient – Current needs are not being met \nPassed as observation with OASIS/HAVE XML tag:’Staffing’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","Decontamination Capacity ","Capacity for chemical/biological/ radiological patient decontamination. \nInactive - Not being used, but available if needed \nOpen - In use and able to accept additional patients \nFull - In use at maximum capacity \nExceeded - Needs exceed available capacity \nPassed as observation with OASIS/HAVE XML tag: ‘DeconCapacity’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","EMS Traffic Status ","Facility capable of: \nNormal - Accepting all EMS traffic \nAdvisory - Experiencing specific resource limitations which may affect transport of some EMS traffic. \nClosed - Requesting re-route of EMS traffic to other facilities. \nNot Applicable - Not Applicable. This hospital does not have an emergency department. \nPassed as observation with OASIS/HAVE XML tag: ‘EMSTrafficStatus’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","EMS Capacity ","The number of each triage patient type the hospital can accept. \ntriageRed (numeric) \ntriageYellow (numeric) \ntriageGreen (numeric) \ntriageBlack (numeric) \ncommentText (string) \nPassed as observation with OASIS/HAVE XML tags: ‘CapacityTriageRed’ \n‘CapacityTriageYellow’ \n‘CapacityTriageGreen’ \n‘CapacityTriageBlack’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","EMS Census ","The number of each triage patient type the overall hospital currently has. \ntriageRed (numeric) \ntriageYellow (numeric) \ntriageGreen (numeric) \ntriageBlack (numeric) \ncommentText (string) \nPassed as observation with OASIS/HAVE XML tags: ‘CensusTriageRed’ \n‘CensusTriageYellow’ \n‘CensusTriageGreen’ \n‘CensusTriageBlack’ \nAssociated comment may also be passed. "]
["Foundational","Hospital Census/Utilization","Adult ICU ","Capacity Status for adult ICU beds. [These can support critically ill or injured patients, including ventilator support. This category includes all major subtypes of ICU beds, including neuro, cardiac, trauma, or medical, with the exception that this category does not include burn ICU beds.] "]
["Foundational","Hospital Census/Utilization","Medical Surgical ","Capacity Status for adult medical-surgical beds. [These are also thought of as ward beds. These beds may or may not include cardiac telemetry capability.] "]
["Foundational","Hospital Census/Utilization","Burn ","Capacity Status for burn beds. [These are thought of as Burn ICU beds, either approved by the American Burn Association or self-designated. These beds are NOT to be included in other ICU bed counts.] "]
["Foundational","Hospital Census/Utilization","Pediatric ICU ","Capacity Status for pediatric ICU beds. [Similar to adult ICU beds, but for patients 17-years-old and younger.] "]
["Foundational","Hospital Census/Utilization","Pediatrics ","Capacity Status for pediatrics beds. [These are ward medical/surgical beds for patients 17-years-old and younger.] "]
["Foundational","Hospital Census/Utilization","Negative Flow Isolation ","Capacity status for negative airflow isolation beds. [These provide respiratory isolation. NOTE: This value may represent available beds included in the counts of other types.] "]
["Foundational","Hospital Census/Utilization","Available Ventilators ","Functional ventilators not in current use. "]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]
[null,null,null,""]

{"sheet":"EOI-Questionnaire","index":9,"n_rows":147,"n_cols":16,"rows_kept":147,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Data Category","Element Category","Data Element","HL7 Context","Q#","Question","Answer","Application","Comments","Q1","Q2","Q3","Q4","Q5","QKey","Data Source"]
["Foundational"]
[null,"Demographic Data"]
[null,null,"BioSense Patient ID","PID-3",1,"Where is the best place (in messages) to find the MRN for this patient's visit?  PID-2, PID-3?  If using PID-3, will there be multiple repetitions?  If so, what is the type (component 5) and assigning authority (component 4) we should use?  Any other assumptions?",null,null,null,"Where is the best place (in messages) to find the MRN for this patient's visit?  PID-2, PID-3?  If using PID-3, will there be multiple repetitions?  If so, what is the type (component 5) and assigning authority (component 4) we should use?  Any other"," assumptions?",null,null,null,5,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",2,"Are your MRN and Account numbers numeric or alpha-numeric?",null,null,null,"Are your MRN and Account numbers numeric or alpha-numeric?",{"$nulls":4},4,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",3,"Do any facilities share assigning authorities for either MRN or Account numbers?",null,null,null,"Do any facilities share assigning authorities for either MRN or Account numbers?",{"$nulls":4},3,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",4,"If the assigning authority is not in PID-3.4, can we use MSH-4.",null,null,null,"If the assigning authority is not in PID-3.4, can we use MSH-4.",{"$nulls":4},76,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",5,"Will your HIS send outside patients?  If yes, what will the patient number that is sent look like?  Please give an example.",null,null,null,"Will your HIS send outside patients?  If yes, what will the patient number that is sent look like?  Please give an example.",{"$nulls":4},15,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",6,"Are there special Patient IDs or ID ranges that required special processing?\nFor example, all MRNs staring with 5 are test patients and will not go to BioSense.",null,null,null,"Are there special Patient IDs or ID ranges that required special processing?\nFor example, all MRNs staring with 5 are test patients and will not go to BioSense.",{"$nulls":4},21,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"BioSense Patient ID","PID-3",7,"Is the MRN normalized?  For example, do the leading zeros need to be removed or the number formated?",null,null,null,"Is the MRN normalized?  For example, do the leading zeros need to be removed or the number formated?",{"$nulls":4},1,"<Data Source>"]
[null,null,"BioSense Patient ID","PID-3",8,"Are MRNs ever used to represent non-patients (e.g. guarantors, bone marrow donors, lab animals)?",null,null,null,"Are MRNs ever used to represent non-patients (e.g. guarantors, bone marrow donors, lab animals)?",{"$nulls":4},74,"<Data Source>"]
[null,null,"BioSense Visit ID","PID-18",1,"Is the Account # normalized?  For example, do the leading zeros need to be removed or the number formated?",null,null,null,"Is the Account # normalized?  For example, do the leading zeros need to be removed or the number formated?",{"$nulls":4},70,"<Data Source>"]
[null,null,"BioSense Visit ID","PID-18",2,"Does HIS ever inactivate or close an account number or episode?  For example, the account is opened in error, will HIS inactivate the account?\nIf yes, will this be sent across the interface? If yes, what trigger event will be sent?",null,null,null,"Does HIS ever inactivate or close an account number or episode?  For example, the account is opened in error, will HIS inactivate the account?\nIf yes, will this be sent across the interface? If yes, what trigger event will be sent?",{"$nulls":4},17,"<Data Source>"]
[null,null,"BioSense Visit ID","PID-18",3,"If the assigning authority is not in PID-18.4, can we use MSH-4.",null,null,null,"If the assigning authority is not in PID-18.4, can we use MSH-4.",{"$nulls":4},72,"<Data Source>"]
[null,null,"BioSense Visit ID","PID-18",4,"Do patients get a different account number for each visit (episode of care)?  The Linker is designed for account numbers on the visit level and not the patient level.",null,null,null,"Do patients get a different account number for each visit (episode of care)?  The Linker is designed for account numbers on the visit level and not the patient level.",{"$nulls":4},16,"<Data Source>"]
[null,null,"BioSense Visit ID","PID-18",5,"Are there any fluctuations in visits or transactions we should know about, e.g., due to free screenings, discharging series patients.",null,null,null,"Are there any fluctuations in visits or transactions we should know about, e.g., due to free screenings, discharging series patients.",{"$nulls":4},344,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Address","PID-11",1,"Will there be multiple repetitions?  Should we use the 1st repetition?  If not, what is the type we should use?",null,null,null,"Will there be multiple repetitions?  Should we use the 1st repetition?  If not, what is the type we should use?",{"$nulls":4},47,"<Data Source>"]
[null,null,"Zip code","PID-11.5",1,"Are there multiple repeitions of the patient's address?  If so, can we use the 1st address in the list?  If not, what is the logic to choose the address?",null,null,null,"Are there multiple repeitions of the patient's address?  If so, can we use the 1st address in the list?  If not, what is the logic to choose the address?",{"$nulls":4},48,"<Data Source>"]
[null,null,"State","PID-11.4",1,"Is country or state or province stored in the same field?  If so, how are they distinguished?",null,null,null,"Is country or state or province stored in the same field?  If so, how are they distinguished?",{"$nulls":4},35,"<Data Source>"]
[null,null,"County","PID-11.9",1,"Is county code derived from the Zip code?",null,null,null,"Is county code derived from the Zip code?",{"$nulls":4},24,"<Data Source>"]
[null,null,"Patient Death Indicator","PID-30",1,"Is the absense of any values in PID-30 is an indication of non-deaths or the field is not being used?",null,null,null,"Is the absense of any values in PID-30 is an indication of non-deaths or the field is not being used?",{"$nulls":4},348,"<Data Source>"]
[null,null,"Patient Death Indicator","PID-30",2,"Does this field correlate with the values for expired found in PV1-36 (Discharge Disposition)?",null,null,null,"Does this field correlate with the values for expired found in PV1-36 (Discharge Disposition)?",{"$nulls":4},350,"<Data Source>"]
[null,null,"Deceased Date","PID-29",1,"Is this field populated when PID-30 (patient death indicator) = Y and/or when the PV1-36 (Discharge Disposition) is a value for expired?",null,null,null,"Is this field populated when PID-30 (patient death indicator) = Y and/or when the PV1-36 (Discharge Disposition) is a value for expired?",{"$nulls":4},351,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Discharge date/time","PV1-45",1,"Does your system batch generate discharges?",null,null,null,"Does your system batch generate discharges?",{"$nulls":4},336,"<Data Source>"]
[null,null,"Discharge date/time","PV1-45",2,"Are discharges auto-generated?",null,null,null,"Are discharges auto-generated?",{"$nulls":4},338,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",1,"If chief complaint is not sent in PV2-segment can we obtain this from elsewhere in the message, such as in a DG1-segment?",null,null,null,"If chief complaint is not sent in PV2-segment can we obtain this from elsewhere in the message, such as in a DG1-segment?",{"$nulls":4},301,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",2,"What is the name on the screen of the field where people enter Chief Complaint?",null,null,null,"What is the name on the screen of the field where people enter Chief Complaint?",{"$nulls":4},304,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",3,"How is it entered in the hospital - free text, drop down menu, ICD-9?",null,null,null,"How is it entered in the hospital - free text, drop down menu, ICD-9?",{"$nulls":4},307,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",4,"Is PV2-3 a code or a chief complaint (CC) text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",null,null,null,"Is PV2-3 a code or a chief complaint (CC) text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",{"$nulls":4},310,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",5,"What system in the hospital is being used to enter the CC ?",null,null,null,"What system in the hospital is being used to enter the CC ?",{"$nulls":4},313,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Chief Complaint","PV2-3",6,"What is the workflow for assigning the Chief Complaint?",null,null,null,"What is the workflow for assigning the Chief Complaint?",{"$nulls":4},315,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",7,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",{"$nulls":4},317,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",8,"How is the Chief Complaint identified in the messages?",null,null,null,"How is the Chief Complaint identified in the messages?",{"$nulls":4},319,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",9,"Which messages contain the Chief Complaint (e.g. A01, P01)?",null,null,null,"Which messages contain the Chief Complaint (e.g. A01, P01)?",{"$nulls":4},321,"<Data Source>"]
[null,null,"Chief Complaint","PV2-3",10,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",null,null,null,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",{"$nulls":4},323,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",1,"If chief complaint is not sent in PV2-segment can we obtain this from elsewhere in the message, such as in a DG1-segment?",null,null,null,"If chief complaint is not sent in PV2-segment can we obtain this from elsewhere in the message, such as in a DG1-segment?",{"$nulls":4},300,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",2,"What is the name on the screen of the field where people enter Chief Complaint?",null,null,null,"What is the name on the screen of the field where people enter Chief Complaint?",{"$nulls":4},303,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Admission Reason","PV2-3",3,"How is it entered in the hospital - free text, drop down menu, ICD-9?",null,null,null,"How is it entered in the hospital - free text, drop down menu, ICD-9?",{"$nulls":4},306,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",4,"Is PV2-3 a code or a chief compliant text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",null,null,null,"Is PV2-3 a code or a chief compliant text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",{"$nulls":4},309,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",5,"What system in the hospital is being used to enter the CC ?",null,null,null,"What system in the hospital is being used to enter the CC ?",{"$nulls":4},312,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",6,"What is the workflow for assigning the Chief Complaint?",null,null,null,"What is the workflow for assigning the Chief Complaint?",{"$nulls":4},314,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",7,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",{"$nulls":4},316,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",8,"How is the Chief Complaint identified in the messages?",null,null,null,"How is the Chief Complaint identified in the messages?",{"$nulls":4},318,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",9,"Which messages contain the Chief Complaint (e.g. A01, P01)?",null,null,null,"Which messages contain the Chief Complaint (e.g. A01, P01)?",{"$nulls":4},320,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Admission Reason","PV2-3",10,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",null,null,null,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",{"$nulls":4},322,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",11,"What is the workflow for assigning the Admission Reason?",null,null,null,"What is the workflow for assigning the Admission Reason?",{"$nulls":4},302,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",12,"Who (Triage, Admissions, Physician, etc) assigns the Admission Reason?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Admission Reason?",{"$nulls":4},305,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",13,"How is the Admission Reason identified in the messages?",null,null,null,"How is the Admission Reason identified in the messages?",{"$nulls":4},308,"<Data Source>"]
[null,null,"Admission Reason","PV2-3",14,"Which messages contain the Admission Reason (e.g. A01, P01)?",null,null,null,"Which messages contain the Admission Reason (e.g. A01, P01)?",{"$nulls":4},311,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",1,"What is the workflow for assigning the Discharge Diagnosis?",null,null,null,"What is the workflow for assigning the Discharge Diagnosis?",{"$nulls":4},275,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",2,"Who (Triage, Admissions, Physician, etc) assigns the Discharge Diagnosis?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Discharge Diagnosis?",{"$nulls":4},278,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Discharge Diagnosis","DG1-3",3,"How is the Discharge Diagnosis identified in the messages?",null,null,null,"How is the Discharge Diagnosis identified in the messages?",{"$nulls":4},281,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",4,"Which messages contain the Discharge Diagnosis (e.g. A01, P01)?",null,null,null,"Which messages contain the Discharge Diagnosis (e.g. A01, P01)?",{"$nulls":4},284,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",5,"Is the Discharge Diagnosis done at time of discharge or post discharge?  If so, what system holds the Discharge Diagnosis?",null,null,null,"Is the Discharge Diagnosis done at time of discharge or post discharge?  If so, what system holds the Discharge Diagnosis?",{"$nulls":4},287,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",6,"What release of ICD-9?",null,null,null,"What release of ICD-9?",{"$nulls":4},290,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",7,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",null,null,null,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",{"$nulls":4},293,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",8,"How is the ICD-9 or CPT-4 code determined in DG1-3?",null,null,null,"How is the ICD-9 or CPT-4 code determined in DG1-3?",{"$nulls":4},296,"<Data Source>"]
[null,null,"Discharge Diagnosis","DG1-3",9,"Will there be textual description and, if so, would it represent the standard ICD9 description?",null,null,null,"Will there be textual description and, if so, would it represent the standard ICD9 description?",{"$nulls":4},340,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Discharge Diagnosis priority","DG1-15",1,"Do you use diagnosis priority of 0 and, if so, is it limited to the discharge diagnosis?",null,null,null,"Do you use diagnosis priority of 0 and, if so, is it limited to the discharge diagnosis?",{"$nulls":4},272,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",1,"What is the workflow for assigning the Working Diagnosis?",null,null,null,"What is the workflow for assigning the Working Diagnosis?",{"$nulls":4},274,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",2,"Who (Triage, Admissions, Physician, etc) assigns the Working Diagnosis?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Working Diagnosis?",{"$nulls":4},277,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",3,"How is the Working Diagnosis identified in the messages?",null,null,null,"How is the Working Diagnosis identified in the messages?",{"$nulls":4},280,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",4,"Which messages contain the Working Diagnosis (e.g. A01, P01)?",null,null,null,"Which messages contain the Working Diagnosis (e.g. A01, P01)?",{"$nulls":4},283,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",5,"Is the Working Diagnosis done during the episode of care?  If so, what system holds the Working Diagnosis?",null,null,null,"Is the Working Diagnosis done during the episode of care?  If so, what system holds the Working Diagnosis?",{"$nulls":4},286,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",6,"What release of ICD-9?",null,null,null,"What release of ICD-9?",{"$nulls":4},289,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Working Diagnosis","DG1-3",7,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",null,null,null,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",{"$nulls":4},292,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",8,"How is the ICD-9 or CPT-4 code determined in DG1-3?",null,null,null,"How is the ICD-9 or CPT-4 code determined in DG1-3?",{"$nulls":4},295,"<Data Source>"]
[null,null,"Working Diagnosis","DG1-3",9,"Will there be textual description and, if so, would it represent the standard ICD9 description?",null,null,null,"Will there be textual description and, if so, would it represent the standard ICD9 description?",{"$nulls":4},341,"<Data Source>"]
[null,null,"Working Diagnosis priority","DG1-15",1,"Do you use diagnosis priority of 0 and, if so, is it limited to the working diagnosis?",null,null,null,"Do you use diagnosis priority of 0 and, if so, is it limited to the working diagnosis?",{"$nulls":4},271,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",1,"What is the workflow for assigning the Admitting Diagnosis?",null,null,null,"What is the workflow for assigning the Admitting Diagnosis?",{"$nulls":4},273,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",2,"Who (Triage, Admissions, Physician, etc) assigns the Admitting Diagnosis?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Admitting Diagnosis?",{"$nulls":4},276,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",3,"How is the Admitting Diagnosis identified in the messages?",null,null,null,"How is the Admitting Diagnosis identified in the messages?",{"$nulls":4},279,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Admitting Diagnosis","DG1-3",4,"Which messages contain the Admitting Diagnosis (e.g. A01, P01)?",null,null,null,"Which messages contain the Admitting Diagnosis (e.g. A01, P01)?",{"$nulls":4},282,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",5,"Is the Admitting Diagnosis done at time of Admission?  If so, what system holds the Admitting Diagnosis?",null,null,null,"Is the Admitting Diagnosis done at time of Admission?  If so, what system holds the Admitting Diagnosis?",{"$nulls":4},285,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",6,"What release of ICD-9?",null,null,null,"What release of ICD-9?",{"$nulls":4},288,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",7,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",null,null,null,"Do you have a separate coding/abstracting system from the HIS?  Does it have a Medical Records outbound interface?",{"$nulls":4},291,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",8,"How is the ICD-9 or CPT-4 code determined in DG1-3?",null,null,null,"How is the ICD-9 or CPT-4 code determined in DG1-3?",{"$nulls":4},294,"<Data Source>"]
[null,null,"Admitting Diagnosis","DG1-3",9,"Will there be textual description and, if so, would it represent the standard ICD9 description?",null,null,null,"Will there be textual description and, if so, would it represent the standard ICD9 description?",{"$nulls":4},342,"<Data Source>"]
[null,null,"Admitting Diagnosis priority","DG1-15",1,"Do you use diagnosis priority of 0 and, if so, is it limited to the admitting diagnosis?",null,null,null,"Do you use diagnosis priority of 0 and, if so, is it limited to the admitting diagnosis?",{"$nulls":4},270,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Diagnosis At Time Of Discharge","DG1-3",1,"Will there be textual description and, if so, would it represent the standard ICD9 description?",null,null,null,"Will there be textual description and, if so, would it represent the standard ICD9 description?",{"$nulls":4},343,"<Data Source>"]
[null,null,"Patient Class","PV1-2",1,"Will observation and urgent care patient's have an \"E\" patient class?  If so, how can we determine an \"ED Only\" patient?",null,null,null,"Will observation and urgent care patient's have an \"E\" patient class?  If so, how can we determine an \"ED Only\" patient?",{"$nulls":4},81,"<Data Source>"]
[null,null,"Patient Class","PV1-2",2,"Is the patient class field alone enough to determine if the patient is an Inpatient, Outpatient or ED?  If not, what other fields can be used?  For example, the patient type and patient class can be used together to determine the patient type.",null,null,null,"Is the patient class field alone enough to determine if the patient is an Inpatient, Outpatient or ED?  If not, what other fields can be used?  For example, the patient type and patient class can be used together to determine the patient type.",{"$nulls":4},80,"<Data Source>"]
["Foundational",{"$nulls":4},""]
[null,"Hospital Census/Utilization",null,null,null,""]
[null,null,"Date/time of report","OBR-7",1,"Please explain the meaning for the report date/time. It is understood it may vary but it covers either the previous 24 hour period or the previous calendar day.",null,null,null,"Please explain the meaning for the report date/time. It is understood it may vary but it covers either the previous 24 hour period or the previous calendar day.",{"$nulls":4},59,"<Data Source>"]
[null,null,"Date/time of report","OBR-7",2,"The report date should be the date of the census report/extract, not the current date of the time the message is being created (that goes in MSH-7). If the report if for 09/01/06 and the report/extract is 09/01/06 at 11:59, then OBR-7 would be 200609011159.  If the extract is done after midnight such as at 12:20am, the report date should be 200609020020.",null,null,null,"The report date should be the date of the census report/extract, not the current date of the time the message is being created (that goes in MSH-7). If the report if for 09/01/06 and the report/extract is 09/01/06 at 11:59, then OBR-7 would be 200609","011159.  If the extract is done after midnight such as at 12:20am, the report date should be 200609020020.",null,null,null,339,"<Data Source>"]
[null,null,"Occupancy","OBX-5",1,"Please explain the calculation for occupancy rate.",null,null,null,"Please explain the calculation for occupancy rate.",{"$nulls":4},62,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Number of patients","OBX-5",1,"Define Number of patients (occupied beds)",null,null,null,"Define Number of patients (occupied beds)",{"$nulls":4},346,"<Data Source>"]
[null,null,"Number of beds available","OBX-5",1,"Define Number of beds available",null,null,null,"Define Number of beds available",{"$nulls":4},345,"<Data Source>"]
["ED/Clinical",{"$nulls":4},""]
[null,"ED/Clinical Data",null,null,null,""]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",1,"What is the workflow for assigning the Chief Complaint?",null,null,null,"What is the workflow for assigning the Chief Complaint?",{"$nulls":4},324,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",2,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",null,null,null,"Who (Triage, Admissions, Physician, etc) assigns the Chief Complaint?",{"$nulls":4},325,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",3,"How is the Chief Complaint identified in the messages?",null,null,null,"How is the Chief Complaint identified in the messages?",{"$nulls":4},326,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",4,"Which messages contain the Chief Complaint (e.g. A01, P01)?",null,null,null,"Which messages contain the Chief Complaint (e.g. A01, P01)?",{"$nulls":4},327,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",5,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",null,null,null,"In the ER registration process, does the patient give a verbal chief complaint to a triage/registration desk?",{"$nulls":4},328,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",6,"If chief complaint is not sent in PV2-segment can we get it in a DG1-segment?",null,null,null,"If chief complaint is not sent in PV2-segment can we get it in a DG1-segment?",{"$nulls":4},83,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",7,"What is the name on the screen of the field where people enter Chief Complaint?",null,null,null,"What is the name on the screen of the field where people enter Chief Complaint?",{"$nulls":4},85,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",8,"How is it entered in the hospital - free text, drop down menu, ICD-9?",null,null,null,"How is it entered in the hospital - free text, drop down menu, ICD-9?",{"$nulls":4},86,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",9,"Is PV2-3 a code or a chief complaint (CC) text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",null,null,null,"Is PV2-3 a code or a chief complaint (CC) text?  If text, is the text in the PV2-3.2 component?\nRefer to Messaging Guide section 2.3.",{"$nulls":4},38,"<Data Source>"]
[null,null,"ED Chief Complaint-Patient Reported","OBX-5",10,"What system in the hospital is being used to enter the CC ?",null,null,null,"What system in the hospital is being used to enter the CC ?",{"$nulls":4},84,"<Data Source>"]
[null,null,"Procedures performed","OBR-44 or OBR-31",1,"How is the ICD-9 or CPT-4 code determined in PR1-3?",null,null,null,"How is the ICD-9 or CPT-4 code determined in PR1-3?",{"$nulls":4},347,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Procedures performed","PR1-3",1,"How is the ICD-9 or CPT-4 code determined in PR1-3?",null,null,null,"How is the ICD-9 or CPT-4 code determined in PR1-3?",{"$nulls":4},40,"<Data Source>"]
[null,null,"Procedure date/time","PR1-5",1,"Is Prodcedure Date/Time populated? If not, can Admit Date be copied to this field?",null,null,null,"Is Prodcedure Date/Time populated? If not, can Admit Date be copied to this field?",{"$nulls":4},33,"<Data Source>"]
["Lab/Micro",{"$nulls":4},""]
[null,"Lab/Micro Orders",null,null,null,""]
[null,null,"Reason for Test","OBR-31",1,"Are you employing a coding standard for Reason for Study (OBR-31)?  If so, please provide.",null,null,null,"Are you employing a coding standard for Reason for Study (OBR-31)?  If so, please provide.",{"$nulls":4},329,"<Data Source>"]
["Lab/Micro",{"$nulls":4},""]
[null,"Lab/Micro Results",null,null,null,""]
[null,null,"Diagnostic Service Section ID","OBR-24",1,"Is the department easily identified in the OBR-24 for filtering?  If not, what other field(s) can be used for filtering?\nRefer to section 2.7 of the Messaging Guide.",null,null,null,"Is the department easily identified in the OBR-24 for filtering?  If not, what other field(s) can be used for filtering?\nRefer to section 2.7 of the Messaging Guide.",{"$nulls":4},57,"<Data Source>"]
[null,null,"Resulted Test Code/Name","OBX-3",1,"Are there are \"special\" OBX-3 requirements.\nFor example, the combination of OBX-3 and OBX-4 must be unique under a single OBR.  In some microbiology results, OBX-3 values are replicated amongst several OBXs within an OBR with the same OBX-4.",null,null,null,"Are there are \"special\" OBX-3 requirements.\nFor example, the combination of OBX-3 and OBX-4 must be unique under a single OBR.  In some microbiology results, OBX-3 values are replicated amongst several OBXs within an OBR with the same OBX-4.",{"$nulls":4},27,"<Data Source>"]
[{"$nulls":5},""]
[null,null,"Result other than organism","OBX-5",1,"Will OBX-5 contain any patient identifiable information?",null,null,null,"Will OBX-5 contain any patient identifiable information?",{"$nulls":4},330,"<Data Source>"]
[null,null,"Result other than organism","OBX-5",2,"Does OBX-5 repeat?  If so, what is the meaning of the repitions.  For example, each repitition is a separate line.",null,null,null,"Does OBX-5 repeat?  If so, what is the meaning of the repitions.  For example, each repitition is a separate line.",{"$nulls":4},331,"<Data Source>"]
[null,null,"Result other than organism","OBX-5",3,"Are the lab results in the current interface a discrete/coded value?\nIf not, can the result's discrete value be determined from other fields and/or translation table?\nIf not, is it possible to explore obtaining the discrete data?",null,null,null,"Are the lab results in the current interface a discrete/coded value?\nIf not, can the result's discrete value be determined from other fields and/or translation table?\nIf not, is it possible to explore obtaining the discrete data?",{"$nulls":4},332,"<Data Source>"]
["Pharmacy",{"$nulls":4},""]
[null,"Medication Orders",null,null,null,""]
[null,null,"Drug code/name","RXO-1",1,"Do you employ the use of a standard pharmacy coding system?  If so, what is the coding system?  If so, where in the HL7 message is it sent.",null,null,null,"Do you employ the use of a standard pharmacy coding system?  If so, what is the coding system?  If so, where in the HL7 message is it sent.",{"$nulls":4},87,"<Data Source>"]
["Radiology",{"$nulls":4},""]
[null,"Radiology Orders",null,null,null,""]
[null,null,"Reason for Test","OBR-31",1,"Are you employing a coding standard for Reason for Study (OBR-31)?  If so, please provide.",null,null,null,"Are you employing a coding standard for Reason for Study (OBR-31)?  If so, please provide.",{"$nulls":4},333,"<Data Source>"]
["Radiology",{"$nulls":4},""]
[null,"Radiology Results",null,null,null,""]
[{"$nulls":5},""]
[null,null,"Diagnostic Service Section ID","OBR-24",1,"Is the department easily identified in the OBR-24 for filtering?  If not, what other field(s) can be used for filtering?\nRefer to section 2.7 of the Messaging Guide.",null,null,null,"Is the department easily identified in the OBR-24 for filtering?  If not, what other field(s) can be used for filtering?\nRefer to section 2.7 of the Messaging Guide.",{"$nulls":4},334,"<Data Source>"]
[null,null,"Procedures","OBR-44",1,"Are you employing a coding standard for Procedures (OBR-44)?  If so, please provide.",null,null,null,"Are you employing a coding standard for Procedures (OBR-44)?  If so, please provide.",{"$nulls":4},335,"<Data Source>"]
["Foundational",{"$nulls":4},""]
[null,"Additional Elements Needed for Communications and Processing",null,null,null,""]
[null,null,"Sending Facility","MSH-4",1,"Do any facilities send messages using something other than their facility mnemonic in the sending facility (MSH-4)?",null,null,null,"Do any facilities send messages using something other than their facility mnemonic in the sending facility (MSH-4)?",{"$nulls":4},268,"<Data Source>"]
[null,null,"Date/Time Of Message","MSH-7",1,"Are seconds included in time fields?",null,null,null,"Are seconds included in time fields?",{"$nulls":4},30,"<Data Source>"]
[null,null,"Patient Name","PID-5",1,"Special Names: Are there special patients that we should be aware of?  For example (VIP Person, Top Secret, Identity Unknown, Test Record, A Dog, etc).  If so, how should these patients be handled?",null,null,null,"Special Names: Are there special patients that we should be aware of?  For example (VIP Person, Top Secret, Identity Unknown, Test Record, A Dog, etc).  If so, how should these patients be handled?",{"$nulls":4},269,"<Data Source>"]
[null,null,"Prior Patient Identifier List","MRG-1",1,"Is the non-survivor MRN in MRG-1?  If not, where is it located? ",null,null,null,"Is the non-survivor MRN in MRG-1?  If not, where is it located? ",{"$nulls":4},267,"<Data Source>"]
[{"$nulls":5},""]

{"sheet":"Contacts","index":10,"n_rows":9,"n_cols":8,"rows_kept":9,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Organization","Title","Role/Responsibility","Name","Phone","Cell Phone","E-mail","\nComments"]
[]
["<Data Source>","Data Source Project Manager","Project Manager","<Name>"]
["BioSense DPIT","Developer","BioSense Developer","BioSense Developer"]
["BioSense DPIT","HL7 Analyst","BioSense HL7 Analyst","BioSense HL7 Analyst"]
["BioSense DPIT","Site Manager","BioSense Site Manager","BioSense Site Manager"]
["BioSense DPIT","Technical Lead","BioSense Technical Lead","BioSense Technical Lead"]
["Constella","Recruitment Representative","Constella Representative","Constella Representative"]
["<Data Source>","Data Source Project Manager","Project Manager","Data Source Project Manager"]

{"sheet":"Ports","index":11,"n_rows":1,"n_cols":6,"rows_kept":1,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["IP Address","Port","Direction","Environment","\nPurpose/Comments","Phase"]

{"sheet":"DS Deliverable Checklist","index":12,"n_rows":89,"n_cols":6,"rows_kept":89,"cut":false,"hidden":false,"merged":[],"flags":["formulas_cached_only"]}
["Checklist Name","CodeSet","HL7 Context","Avail?\n(Y/N)","Rec'd?\n(Y/N)","Comments"]
[]
["Diagrams"]
[null,"Network Diagram"]
[null,"Integration Diagram"]
[null,"Chief Complaint & Diagnosis Flow"]
[null,"ADT Workflow"]
[null,"Lab Orders Workflow"]
[null,"Lab Results Workflow"]
[null,"Medication Orders Workflow"]
["Vocabulary Workbook"]
[null,"Sex","PID-8"]
[null,"State","PID-11.4"]
[null,"County","PID-11.9"]
[null,"Country","PID-11.6"]
[null,"Ethnicity","PID-22"]
[null,"Race Category","PID-10"]
[null,"Yes / No Patient Death Indicator?","PID-30"]
[null,"Yes / No Employment Related Illness","PV2-15"]
[null,"Yes / No Identity Unknown","PID-31"]
[null,"Diagnosis Type","DG1-6"]
[null,"Diagnosis Priority","DG1-15"]
[null,"Discharge Disposition","PV1-36"]
[null,"Medical Specialty","PV1-10"]
[null,"Patient Class","PV1-2"]
[null,"Admission Type","PV1-4"]
[null,"Admission Source","PV1-14"]
[null,"Admission Level of Care","PV2-40"]
[null,"Temperature Identifier","OBX-3"]
[null,"Temperature Unit","OBX-6"]
[]
[null,"Blood Pressure Identifier","OBX-3"]
[null,"Blood Pressure Unit","OBX-6"]
[null,"Pharmacy Order Type","RXO-27"]
[null,"Order Control Code","ORC-1"]
[null,"Diagnostic Service Section","OBR-24"]
[null,"Test Interpretation","OBX-8"]
[null,"Test Status","OBX-11"]
[null,"Result Status","OBR-25"]
["Catalog"]
[null,"Master Lab Orderable Catalog","OBR-4"]
[null,"Lab Result & Comment codes","OBX-5"]
[null,"Micro Organism Codes","OBX-5"]
[null,"Antibiotic Codes","OBX-3"]
[null,"Radiology Order Catalog","OBR-4"]
[null,"Pharmacy Catalog","RXO-1"]
["Filtering"]
[null,"Sending Application","MSH-3"]
[null,"Locations","PV1-3"]
["Interface Specifications"]
[null,"ADT-Admit Patient","ADT^A01"]
[null,"ADT-Transfer Patient","ADT^A02"]
[null,"ADT-Discharge Patient","ADT^A03"]
[null,"ADT-Register Patient","ADT^A04"]
[null,"ADT-Change Outpatient to Inpatient","ADT^A06"]
[null,"ADT-Change Inpatient to Outpatient","ADT^A07"]
[null,"ADT-Update patient Information","ADT^A08"]
[null,"ADT-Cancel Admit Patient","ADT^A11"]
[]
[null,"ADT-Cancel Transfer Patient","ADT^A12"]
[null,"ADT-Cancel Discharge Patient","ADT^A13"]
[null,"ADT-Swap Patients","ADT^A17"]
[null,"ADT-Merge Patients","ADT^A40"]
[null,"ADT-Merge Accounts","ADT^A41"]
[null,"ADT-Move Account","ADT^A44"]
[null,"Census","ORU^R01"]
[null,"ED Urgent Care","ADT^A04"]
[null,"Medical Records Abstracting Diagnosis","?"]
[null,"Lab Orders","ORM^O01"]
[null,"Lab Results","ORU^R01"]
[null,"Rad Orders","ORM^O01"]
[null,"Rad Results","ORU^R01"]
[null,"Med Orders","OMP^O09"]
["Sample Messages"]
[null,"ADT"]
[null,"Census Reports"]
[null,"ED/Clinical"]
[null,"Micro order"]
[null,"Micro result with organism and sensitivity "]
[null,"Serology / Immunology result "]
[null,"Micro Lab send out result"]
[null,"RAD order"]
[null,"RAD result"]
[null,"Pharmacy order"]
[null,"Medical Records Abstracting Diagnosis"]
["Other"]
[null,"Data Use Agreement (DUA)"]
[null,"Business Associate Agreement (BAA)"]
[null,"IT Project Schedule"]