LMS Classical Swine Fever (CSF) Data Submission Program Guide · 2019-04-26 · LMS Classical Swine Fever (CSF) Data Submission Program Guide LMS CSF Messaging Guide V2.1 Page 1 of

LMS Classical Swine Fever (CSF) Data Submission Program Guide

LMS CSF Messaging Guide V2.1 Page 1 of 13

Contents Introduction .................................................................................................................................................. 3

Notification Process for Messaging .......................................................................................................... 3

Acknowledgment Message for Successful LMS Acceptance ................................................................ 4

Acknowledgment Message for Unsuccessful LMS Acceptance ............................................................ 4

Submission/Accession Assumptions ..................................................................................................... 5

CSF Messaging Requirements by Sample Stream ......................................................................................... 6 CSF Slaughter Surveillance ........................................................................................................................ 6

Required Fields to Be Included in the Message .................................................................................... 6

Optional Fields that can be Included in the CSF Slaughter Surveillance Message ............................... 6

CSF Diagnostic Sick Pig Surveillance .......................................................................................................... 7

Required Fields to Be Included in the Message .................................................................................... 7

Optional Fields that can be Included in the CSF Diagnostic Sick Pig Surveillance Message ................. 8

CSF Message Components ............................................................................................................................ 8 APHIS Program OID (ORC.4/EI.3) .............................................................................................................. 8

Referral Numbers (ORC.4/EI.1) ................................................................................................................. 9

Submitting Laboratory (ROL) .................................................................................................................... 9

Samples being submitted to NVSL (SPM.2/EIP.1) ..................................................................................... 9

Animal Identifier (PID.3) ........................................................................................................................... 9

Animal Taxonomy/Species (PID.35) ...................................................................................................... 9

Owner information (NK1) ..................................................................................................................... 9

Unique Specimen Identifiers (SPM.2) ....................................................................................................... 9

Specimen Type (SPM.4): SNOMED Codes .............................................................................................. 10

CSF Tests (RESULT.OBX.3): LOINC Codes ................................................................................................ 10

Test Interpretation (RESULT.OBX.8) HL7 User Defined Table 0078 Codes ......................................... 10

Reason for Submission (OBR.31): Locally Defined Codes ....................................................................... 11

Operation/Facility Site Type (ROL) HL7 User Defined Table 0305 Codes ............................................... 11

Clinical Sign(s) (PATIENT_OBSERVATION.OBX.3) .................................................................................... 11

Age Class (PATIENT_OBSERVATION/OBX) and/or Date of Birth (PID.7) ................................................. 12

Date of Death (PID.29) ............................................................................................................................ 12

Production Class (PID.38), HL7 User Defined Table 0429 Codes ............................................................ 12

Additional Guidance for Special Cases ........................................................................................................ 12 Reporting updated lab testing supporting information .......................................................................... 12

LMS Classical Swine Fever (CSF) Data Submission Program Guide


Reporting repeated testing results on the same specimen .................................................................... 13

Reporting an Internal Control Failure Scenario ...................................................................................... 13

Reporting “No Result Available” ............................................................................................................. 13

Contact Information .................................................................................................................................... 13 Document control ....................................................................................................................................... 13


Introduction This document is a reference guide intended to provide the summary information specific for messaging results to the Laboratory Messaging Services (LMS) for Classical Swine Fever virus (CSF) as part of the combined ASF and CSF slaughter and diagnostic sick pig surveillance or as a Foreign Animal Disease (FAD) Investigation in which screening testing occurs in the NAHLN lab. This guide is intended to be used with the suite of reference material for NAHLN HL7 messaging that is available on the VTSL NAHLN Terminology Services web site at http://vtsl.vetmed.vt.edu/nahln/main.cfm.

Notification Process for Messaging The following list outlines the approval process for messaging to the production system. We strongly encourage the lab to do schema validation on the message prior to sending a test message to expedite the process. Rhapsody can be used for this or there are a number of programming editors and other free tools (such and Notepad ++ and XML Tools) that provide this feature. Please see the ‘Hitchhikers Guide to NAHLN Messaging’ for more details.

Please note that there are two separate validation procedures during this review process. The first validation procedure is automatically performed when the message is submitted to the system. This validation procedure checks to see if the HL7 in the message is compliant with the HL7 standard with reference to the current LMS XML schema. The lab will receive feedback from this process immediately after the message is sent. The second validation procedure is performed to make sure the data needed for analysis and reporting are available and valid. A member of the NAHLN IT messaging support team will check over the message and give feedback to the lab via email.

The following steps are necessary to complete the approval process for messaging CSF results into the production system.

1. The lab will inform NAHLN IT messaging support team at [email protected] that they are ready to start test messaging for CSF.

2. The lab will message CSF test results into the test system at: https://vsapps.aphis.usda.gov/HL7ResultTest The system will validate the message to determine if it is HL7 compliant and will immediately provide feedback to the lab via the Acknowledgement message response. The lab should contact the NAHLN IT messaging support team at [email protected] for assistance if a message cannot be successfully sent. Examples of Acknowledgement responses are described below.

3. Once a successful message is sent (i.e. Acknowledgement message of AA), the lab will send a notification email to [email protected] stating that a message has been sent successfully. That email will include the MSH.10, disease tested for, purpose of message (slaughter, diagnostic sick pig or FAD investigation) and accession number used in the message. A member of the NAHLN IT messaging support team will review the message content and feedback will be provided to the lab via email. The lab is expected to make any corrections described in the feedback and send updated messages as needed.

4. Once content review is completed a “test” slaughter surveillance submission will be created in CLSM and a corresponding “test” submission form provided by email to the lab. The lab will use the information listed on the “test” submission form to create an accession in their LIMS that will be used for sending a “test” message into LMS production at: https://vsapps.aphis.usda.gov/HL7Result

http://vtsl.vetmed.vt.edu/nahln/main.cfm

mailto:[email protected]

https://vsapps.aphis.usda.gov/HL7ResultTest




5. Once a successful message is sent (i.e. Acknowledgement message of AA), the lab will send a notification email to [email protected] stating that a message has been sent successfully. That email will include the MSH.10/s, disease tested (CSF), and accession number used in the message. The submission in VSLS/CLSM-CSF will be reviewed to insure the results fields were correctly populated and feedback will be provided to the lab via email. The lab is expected to make any corrections described in the feedback and send updated messages as needed.

6. The NAHLN Program Office (NPO) will approve the lab to begin messaging into production after the test message is successfully validated in all review procedures.

7. NPO will notify the lab director and technical contact that messaging into production has been approved.

8. The Lab will email [email protected] informing them of the date messaging into production will begin.

Acknowledgment Message for Successful LMS Acceptance An Acknowledgement (ACK) message is returned to the lab to indicate successful or unsuccessful receipt of the message by LMS. If receipt was successful, the ACK message will include an Acknowledgment Code which indicates success (MSA.1 = AA). An abbreviated successful ACK message example is provided below. Included in this example is a Message Control ID (MSA.2=2FA21431-548C-4A17-B879-406521BDEAE2) which is taken from the message header of the original message (MSH.10). This ID may be used by the lab’s staff or the message sending system to match the acknowledgement message to the original message sent. Also included is a communication (ERR.7) containing the accession number and processing mode taken from the original message. The Message Control ID and accession number may be used by the lab’s staff or the message sending system to match the acknowledgement message to the original message sent.

<?xml version='1.0' encoding='UTF-8'?> <ACK_R25 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:hl7='urn:hl7-org:v2xml' xsi:noNamespaceSchemaLocation='ackMessage.xsd'> <MSH> . . . </MSH> <MSA> <MSA.1>AA</MSA.1> <MSA.2>2FA21431-548C-4A17-B879-406521BDEAE2</MSA.2> </MSA> <ERR> <ERR.3>0</ERR.3> <ERR.4>I</ERR.4> <ERR.7>Accession:C1801937 Processing Mode:T</ERR.7> </ERR> </ACK_R25>

Acknowledgment Message for Unsuccessful LMS Acceptance If receipt was unsuccessful, the ACK message will include one of two Acknowledgment Codes to indicate either that there was an error in the message structure or content (MSA.1 = AE) or rejection (MSA.1 = AR). Messages may be rejected either because of a problem with the message type, structure, or




processing ID or because of an LMS issue such as database failure. An abbreviated unsuccessful ACK message example is provided below. Also included in the example is a cryptic, yet sometimes useful description of the problem with the message structure or content. The description in the example below indicates that the required lab specimen ID (SPM.3) and specimen type (SPM.4) are missing (“Invalid content was found starting with element 'SPM.11'. One of '{SPM.3, SPM.4}' is expected.”).

<?xml version='1.0' encoding='UTF-8'?> <ACK_R25 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:hl7='urn:hl7-org:v2xml' xsi:noNamespaceSchemaLocation='ackMessage.xsd'> <MSH> . . . </MSH> <MSA> <MSA.1>AE</MSA.1> <MSA.2>2420962</MSA.2> </MSA> <ERR> <ERR.3> <ERR.3.1>0</ERR.3.1> <ERR.3.2 /> <ERR.3.3>NAHLN</ERR.3.3> </ERR.3> <ERR.4 /> <ERR.7><![CDATA[Error occurred processing message on filter 'NAHLN LMS Base Schema': XML Message validation fails.,Nested exception was 'com.orchestral.rhapsody.module.api_2_0.module.filter.FilterProcessingException': XML Message validation fails.,Nested exception was 'org.xml.sax.SAXParseException': cvc-complex-type.2.4.a: Invalid content was found starting with element 'SPM.11'. One of '{SPM.3, SPM.4}' is expected.]]></ERR.7> </ERR> </ACK_R25>

Submission/Accession Assumptions For CSF Slaughter Surveillance testing only. A submission must exist in the VSLS/CLSM-CSF module in order for messaged results to populate into the system. The collector or submitter will create a submission in VSLS and assign a referral number. This referral number will be included on the submission form and must be included in the message. The general format for submitter created referral numbers is [2 letter (Collection) state][2-3 letter initials][date of collection using 2 digit month, 2 digit day, 4 digit year (i.e. MMDDYYYY)]

• The submission in VSLS will not automatically be closed if an interpretation other than “Neg” or “NDET” is reported. For these instances, someone from the lab will need to manually log into VSLS-CSF, review and close the submission.

Diagnostic lab sick pig surveillance testing: The LMS message receiving approach for the information sent for this sample stream eliminates the need for manual data entry into VSLS/CLSM – CSF to create a submission. As a result, additional submission information is required when messaging results for diagnostic laboratory sick pig surveillance submissions. Testing must be done in conjunction with ASF testing.


Only animals submitted with one or more of the following clinical signs should be identified by the lab as fitting the requirements for inclusion and submission of test results for CSF/ASF diagnostic sick pig surveillance.

Presenting signs Post mortem Lesions Increased mortality rate Lymph nodes, lungs, kidneys, spleen,

myocardium, etc. Fever, lethargy, anorexia, depression, abortion Splenomegaly Lameness, recumbency, paddling Erosions, hemorrhage, necrosis, proliferation Antemortem erythemia, petechiae, hematoma, hemorrhage, epistaxis

Acute or chronic ulcers, button ulcers

CSF Messaging Requirements by Sample Stream

CSF Slaughter Surveillance Required Fields to Be Included in the Message The following fields are required to have valid values in the message. Additional details for some of these fields are found in the following sections.

• APHIS Program Object Identifier OID (ORC.4/EI.3) • Referral number (ORC.4 EI.1) (**required for match up to submission in VSLS/CLSM) • Animal Taxonomy/Species (PID.35) • Specimen and animal identifiers: Within a single accession it must be possible to differentiate

individual animals using the following fields. o Accession number/case number (PV1.19/CX.1) o Specimen Placer (Submitter) ID (SPM.2/EIP.1/EI.1). This will be the barcode from the

submission form. o Specimen Filler (Lab) ID (SPM.2/EIP.2/EI.1)

• Specimen/sample information: All of the following fields must be included in the message. o Specimen type (SPM.4) – SNOMED code (CWE.1) and label (CWE.2) o Test date (OBX.19) if a test result could be obtained (result status = F) o Test performed (OBX.3) – LOINC code (CWE.1) and label (CWE.2) or the test planned to

be performed if a test result could not be obtained (result status = X) o Test result (OBX.5) if a test result could be obtained (result status = F) o Test interpretation (OBX.8) if a test result could be obtained (result status = F)

Optional Fields that can be Included in the CSF Slaughter Surveillance Message The following fields should be included in the message if they are available and may be required based on the schema. Additional details for some of these fields are found in the following sections.

• Animal ID (PID.3/CX.1) • Clinical Signs (PID/OBX) • Specimen collection date (SPM.17/DR.1) • Date specimen received (SPM.18) • Operation/Facility site type for animal location (PROL.13/PL.6) • Age class (PATIENT_OBSERVATION/OBX.5/CWE.2) and/or date of birth (PID.7)


• Production class (PID.38) – code (CWE.1) and label (CWE.2) • Geographical information for location of animal when sample was collected. At least one of the

following fields must be included in the message. o Premises identification number of sample collection site and location information

(ROL.13/PL.10/EI.1) and/or o Collection state (ROL.11/XAD.4)

• Reason for submission (OBR.31) – code (CWE.1) and label (CWE.2)

CSF Diagnostic Sick Pig Surveillance Required Fields to Be Included in the Message The following fields are required to have valid values in the message. This message was designed to include both result information in addition to minimal information about the submission. Additional details for some of these fields are found in the following sections.

• APHIS Program OID for CSF Diagnostic sick pig submissions (ORC.4/EI.3) • FAD investigation number or Referral number (ORC.4 EI.1) For Diagnostic sick pig submissions

only the referral number will be created by the lab. (**required for reimbursement**) • Reason for submission (OBR.31) • Specimen and animal identifiers: Within a single accession it must be possible to differentiate

individual animals using the following fields. An accession number and specimen ID assigned by the lab (Filler) are required. When there is a specimen ID provided by the submitter (Placer it should be used to supplement the lab-assigned Filler ID in order to differentiate animals within an accession. o Lab accession/case number (PV1.19/CX.1) o Animal ID (PID.3/CX.1): required if available o Specimen Placer (Submitter) ID (SPM.2/EIP.1/EI.1) if available o Specimen Filler (Lab) ID (SPM.2/EIP.2/EI.1)

• Animal Taxonomy/Species (PID.35) • Specimen/sample information

o Specimen type (SPM.4) o Date specimen received (SPM.18)

• Order Status (ORC.5): must be completed (CM) • Testing information

o Indicator for Result Available/Status (OBX.11): The result status must be “Final” (F). o Test result value type (Result.OBX.2): only numeric (NM) result values are supported and it

is assumed this value is measured as Ct units. o Test performed (OBX.3) – LOINC code (CWE.1) and label (CWE.2) or the test planned to be

performed if a test result could not be obtained (result status = X) o Test result (OBX.5) if a test result could be obtained (result status = F) o Test interpretation (OBX.8) if a test result could be obtained (result status = F) o Test date (OBX.19) if a test result could be obtained (result status = F)

• Geographical information for the premises location where the animal was located when the sample was collected (Source Premises Role = PREM).


o Premises site identification number and location information (ROL.13/PL.10/EI.1) (**required for reimbursement**)

o Premises physical address (ROL.11/XAD.1_sad1.sad2.sad3 - Message when available o Premises site state (ROL.11/XAD.4)

• Submitter(SUB role) – information for individual who submitted sample to the lab Submitter name (ROL.4.2 & ROL.4.3) Submitter state (ROL.11/4) Submitter zip code (ROL.11.5)

• Submitting lab name – if sample was referred from another lab Submitting lab’s accession number – if sample was referred from another lab

Optional Fields that can be Included in the CSF Diagnostic Sick Pig Surveillance Message The following fields should be included if they are available to be messaged and may be required based on the schema. Additional details for some of these fields are found in the following sections.

• Submitting lab ID or name (ROL.4) – if sample was referred from another lab o Submitting lab’s accession number (ROL.1/EI.1)

• Submitter phone number (ROL = SUB) (ROL.12) • Animal Information

o Date of Death (PID.29). The date of death does not apply to those animals sacrificed or euthanized for necropsy.

o Clinical signs (PID/OBX) • Back Tag or Owner information - Animal’s owner name and location information for location

where the animal normally resides. If you have premises ID for the animal from the back tag or owner information provided to you- send the premises ID in NK 1.4 xad.8; if you know the state send in NK 1.4 xad.4

• Specimen collection Date (SPM.17) –Ideally this is the epidemiologically relevant time that the animal was sampled (e.g. the date the specimen was collected from a living animal either at premises where the animal normally resides; or in the lab, the date a living animal was euthanized for necropsy, if the animal was submitted live to the lab.)

• Testing information: o Testing Method (Result.OBX.17): Only “NVSL CSF PCR” is accepted as the testing method,

but this data element is not required

CSF Message Components

APHIS Program OID (ORC.4/EI.3) The Program Object Identifier (OID) will be very important for routing messages internally to the VS data systems. This must be included in the ORC.4 segment.

• If a sample is submitted and tested as part of the CSF slaughter surveillance program use the following OID: 2.16.840.1.113883.3.5.8.3

• If sample CSF testing is initiated at a diagnostic laboratory for a sick pig, or a part of an FAD investigation use the following OID: 2.16.840.1.113883.3.5.8.3.1


• If one or more samples tested for multiple diseases are to be submitted in the same message, each set of disease specific test results must be included under a unique ORDER group with the applicable program OIDs in each ORC segment.

Referral Numbers (ORC.4/EI.1) • For CSF slaughter surveillance testing only, use the VSLS/CLSM referral number that is provided

on the lab submission paperwork. The standard convention is: [2 letter state code][submitters initials][date using format mmddyyyy] followed by a, b, c if more than one submission was create on the same day). Do NOT generate this number if not provided).

• For CSF Diagnostic Sick Pig surveillance testing the lab must create the required Referral Number using the format described above.

• All samples that are tested for CSF in the NAHLN laboratory that are part of or initiate a Foreign Animal Disease (FAD) investigation and MUST have an FAD number/ RCN number in ORC.4/EI.1 in order to be reimbursed for the test. The FAD number format is generally [2digit year][2letter state][4 digit number]

Submitting Laboratory (ROL) If the sample was referred from another lab for testing, use the ROL segment to identify the submitting laboratory and their accession number with an appropriate role code (ROL.3 = LAB) and an indicator for the type of location (ROL.13.6 = L)

• Submitting Lab ADT ID or Name: If the lab has an AAVLD assigned OID this will be used to identify the lab (ROL.4.1) along with the OID assigning authority (ROL.4.9). Otherwise, the lab name can be sent (ROL.4.2).

• Submitting Lab’s Accession Number (ROL.1/EI.1)

Samples being submitted to NVSL (SPM.2/EIP.1) • All 10-4s must include the specimen BARCODE reported in the message in Specimen Placer

(Submitter) ID (SPM.2/EIP.1/EI.1).

Animal Identifier (PID.3) If available, this is often either the animal identification (tag/number) or the animal group/lot identifier. If not available, this can be the subject identifier as recorded in the LIMS (sent with the laboratory facility OID as the identifier assigning authority in PID.3.4). Otherwise, this can be empty

Animal Taxonomy/Species (PID.35) An indicator that a pig was tested is required. The level of taxonomy (e.g. species, breed) reported will be determined by the level of detail available in the LIMS. By default, the species Sus scrofa (SNOMED code 78678003) may be used. Addition children SNOMED codes are available on the VTSL site,

Owner information (NK1) Animal’s owner name and location information for location where the animal normally resides.

Unique Specimen Identifiers (SPM.2) All samples must be submitted with a UNIQUE laboratory assigned specimen ID (aka Filler ID in EIP.2).


If available, a UNIQUE Submitter barcode/ID (aka Placer ID in SPM.2/EIP.1/EI.1) should be provided. Otherwise, if only a non-unique Submitter/Placer ID is available, that should be provided in SPM.2/EIP.1/EI.1.

For more information, see the current version of ‘Hitchhikers Guide to NAHLN Messaging’ or the “NAHLN/LMS HL7 Implementation Guide for Laboratory Results Messaging".

Specimen Type (SPM.4): SNOMED Codes The specimen type currently approved for the NAHLN CSF surveillance testing protocol is Tonsil. Additional approved sample types for FAD testing are included in the following table. If the codes do not represent the specimens that are to be messaged, please contact NPO for guidance.

Approved sample types for FAD testing.

Text label0F

1 SNOMED Code1F

2 Tissue specimen from Tonsil 811000009103 Tissue specimen from spleen 551000009102

Lymph node tissue sample* 309078004 Tonsil Scraping 4241000009102

*Note - Specific sample testing must follow guidelines provided in the ASF-CSF Surveillance Manual.

CSF Tests (RESULT.OBX.3): LOINC Codes The currently supported LOINC code for CSF testing is in the following table.

LOINC Code2 LOINC Short Name (text label)1 LOINC Long Name

44273-1 CSFV RNA XXX NAA+probe-aCnc

Classical swine fever virus RNA [Units/volume] (viral load) in Unspecified specimen by NAA with probe detection

Test Interpretation (RESULT.OBX.8) HL7 User Defined Table 0078 Codes Reminder, for CSF Slaughter surveillance testing, if an interpretation value other than NEG/NDET is messaged for any sample, the “Test Status” in VSLS will not automatically convert to “Completed”. Manual login will be required to close the submission.

Code2 Text Label1 NDET Not Detected DET Detected IND Indeterminate

In the case of a non-negative result, please contact (NPO) for instructions on how to submit the sample to NVSL and the result via messaging. No tests with a non-negative result are to be messaged without authorization and direction from NPO. This does not apply to “quality control failure” nor “no result available” results (as outlined below) which can be messaged routinely.


Reason for Submission (OBR.31): Locally Defined Codes This field is optional for CSF slaughter surveillance results reporting only as the submission reason will be entered into VSLS when the submission is created. Field is required when messaging CSF results from Diagnostic Laboratory Sick Pig surveillance testing. For messaging Diagnostic Laboratory Sick Pig results the National Surveillance (N) reason should be used.

Code2 Text label1 Description

F FAD Diagnostics

Samples that are submitted as part of the original FAD investigation or for testing directly associated with the outbreak and that meet the requirements for the State/Federal response

T Traceback Epidemiologic traceback investigation

N Surveillance, National Used for submission of specimens by a recognized national animal health surveillance program

Operation/Facility Site Type (ROL) HL7 User Defined Table 0305 Codes The type of facility where the animal was located at the time of sample collection. This field is optional for CSF messaging and would be sent in a ROL segment as ROL.13/PL.6 with Role Code = PREM.

Code2 Text label1 Use for Messaging Results for: M Market/Collection Point FAD E Exhibition FAD N Non-producer participants FAD, Diagnostic Sick Pig P Production Unit FAD, Slaughter, Diagnostic Sick Pig S Slaughter Plant FAD, Slaughter

Clinical Sign(s) (PATIENT_OBSERVATION.OBX.3) Serving as the context for what was observed by a caretaker (e.g. abortion, CNS signs, septicemia) or what was reported to the caretaker (e.g. clinical history), the LOINC listed below should be used in OBX.3, and the narrative text for the clinical signs should be reported in OBX.5.

LOINC Code2 LOINC Short name (Text label)1

Description

10187-3 Review of Systems a relevant collection of signs and functions systematically gathered by an animal health caretaker

Example: <OPU_R25.PATIENT_OBSERVATION>

<OBX> <OBX.2>CWE</OBX.2> <OBX.3>

<CWE.1>10187-3</CWE.1> <CWE.2>Review of Systems</CWE.2> <CWE.3>LN</CWE.3>

</OBX.3> <OBX.5>abortion, septicemia</OBX.5> <OBX.11>F</OBX.11>

</OBX> </OPU_R25.PATIENT_OBSERVATION>


Age Class (PATIENT_OBSERVATION/OBX) and/or Date of Birth (PID.7) These fields are optional for CSF messaging. If the lab’s LIMS can capture age class, please sent this information. The LOINC listed below should be used in OBX.3 and one the following codes should be sent as patient observation in (OBX.5). Do not convert age class to date of birth (DOB).

LOINC Code2 LOINC Short name (Text label)1 Description

46251-5 Age Group

Age Class

Description SNOMED Code2 Text label1 Sow/Boar 28811000009104 Adult pig for meat production (organism)

Grower/Finisher 356661000009103 Grower/finisher pig for meat production (organism)

Nursery 28901000009106 Starting pig for meat production (organism)

Suckling 28911000009108 Suckling pig for meat production (organism)

If the lab’s LIMS captures DOB, please send the raw date and do not convert it to age class. The DOB may need to be approximated.

If both age class and DOB are available, please send both.

Date of Death (PID.29) If available, provide the date of death for animals that are submitted dead. The date of death does not apply to those animals sacrificed or euthanized for necropsy.

Production Class (PID.38), HL7 User Defined Table 0429 Codes This field is optional for CSF messaging

Code2 Text label1 Description

BR Breeding/genetic stock Animal intended for use for reproductive purposes to produce offspring.

C Companion Animal intended for personal pleasure, recreation or hobby use. MT Meat Animal intended to be slaughtered for human consumption. MP Multipurpose Animal used for multiple purposes. U Unknown Purpose of the animal is unknown.

Additional Guidance for Special Cases

Reporting updated lab testing supporting information If updated or corrected supporting information needs to be reported (e.g. the collection site premises ID PIN; this does not include test result), the entire accession must be resent with the order status set to ‘replacement’ included in each order segment (ORC.1 = “RO” i.e. “Order has been replaced”). All previously populated data fields must be resent, along with the new value replacing the incorrect or missing value previously sent. Refer to the ‘NAHLN/LMS HL7 Implementation Guide for Laboratory Result Messaging’ for more details. Prior to sending a replacement message contact the NPO for guidance.


Reporting repeated testing results on the same specimen If a specimen is tested more than once and then finalized, additional testing results should be maintained, with the new testing result uniquely identified using the Observation Instance Identifier (OBX.21). Refer to the ‘Hitchhiker’s Guide to NAHLN Messaging’ (Repeated Testing or Re-Sent Results) and the ‘NAHLN/LMS HL7 Implementation Guide For Laboratory Result Messaging’ for more details.

Reporting an Internal Control Failure Scenario If a result cannot be reported because of an internal control failure (e.g. it was not possible to run the test as needed to obtain a valid result) report this with an indicator that a result could not be obtained (OBX.11 = “X”) because of a ‘Quality Control Failure’ (OBX.8 = “QCF”)

Reporting “No Result Available” If a result cannot be reported for any reason other than Quality Control Failure, report this with an indicator that a result could not be obtained (OBX.11 = “X”) with an empty or excluded result interpretation (OBX.8 IS NULL or the OBX.8 tags not sent).

Contact Information To contact the NAHLN Program Office (NPO), please send an email to [email protected].

To contact the NAHLN IT team or the LMS support group, please send an email to [email protected].

Document control

Date Change Explanation Responsible Party 8.21.2018 1.0 Replaces Idiot's Guide to CSF messaging

(Simple 'how do I do it' guides) Cindy Chard-Bergstrom

3.26.19 2.0 Delineate messaging requirements for Slaughter and Diagnostic Sick Pig messaging for routing purposes. Updated required fields and Program OIDs. Guide provided for routing testing

NAHLN Program Office – designee

4.11.2019 2.1 Delineate messaging requirements for Slaughter and Diagnostic Sick Pig messaging for routing purposes. Updated required fields and Program OIDs.

NAHLN Program Office – designee

1 Suggested HL7 value for label field. If other labels are used, they should be related to the specific code provided in the message. 2 Value for HL7 code field.



Documents

LMS Classical Swine Fever (CSF) Data Submission Program Guide · 2019-04-26 · LMS Classical Swine Fever (CSF) Data Submission Program Guide LMS CSF Messaging Guide V2.1 Page 1 of