Skip to content
NordLIS Powered by LabSolution

For Philippine laboratories

Modern LIS. For Philippine laboratories.

Bring orders, analyzer results, and review into one workflow. International data standards, with Philippine patient addresses and a test catalog configured for your laboratory.

Explore the standards

Clarity at every step. Powered by LabSolution

Discover NordLIS

01 · For your laboratory

International standards.
Local working detail.

NordLIS is LabSolution’s modern laboratory information system for the Philippine market, from patient registration to the released report.

Philippine patient addresses

Record region, province, city or municipality, and barangay with a structured address directory.

Your laboratory’s configuration

Set up test catalogs, reference ranges, laboratory sections, and report signers around your team’s work.

Your analyzer connections

Connect through the analyzer bridge, with test and unit mappings defined for each instrument in scope.

02 · Standards in practice

A result needs
more than a number.

The test identity, unit of measure, and source instrument belong with the result. NordLIS preserves that context through analyzer intake and review.

Illustrative mapping No patient data

White blood cell count

Instrument code
WBC
LOINC identity
6690-2
Instrument unit
10^9/L
UCUM unit
10*9/L
Intake format
FHIR R4

The original code and unit stay with the result. Mappings are checked against the instrument and test method during implementation.

LOINC

Identify the test

Map local analyzer codes to standard observation identifiers. Tests without an assigned LOINC remain identified by their local code.

How NordLIS uses LOINC

Test catalogs and analyzer mappings carry LOINC identifiers. Mapping review must confirm the test’s meaning; a valid code alone does not confirm a clinical match.

About the LOINC standard ↗

UCUM

Keep units explicit

Map instrument units to a consistent code for electronic exchange, while preserving the original unit sent by the analyzer.

How NordLIS uses UCUM

Analyzer unit mappings provide UCUM codes alongside the source unit. Catalog unit symbols retain their entered case, such as g/L and mmol/L.

About the UCUM standard ↗

FHIR R4

Structure the result

The analyzer bridge delivers structured result bundles to NordLIS, with observations and their instrument and specimen context.

What FHIR support covers

Current support covers analyzer-result intake using FHIR R4 bundles. General-purpose FHIR export and hospital-system connectors are outside the current release scope.

About FHIR observations ↗

HL7 / ASTM

Connect the instrument

The analyzer bridge handles HL7 v2 and ASTM messaging for configured instrument profiles. Each connection needs its own mapping and acceptance tests.

What an instrument connection includes

Confirm the instrument model, protocol, message format, test menu, and direction of exchange. Supported behavior depends on the selected profile and site validation.

03 · Daily laboratory work

From the first order to the released report.

Follow the work through NordLIS: register the patient, prepare the order, review results, and release the report. Explore each step below.

Register and order

Keep patient details, requested tests, and sample identifiers together.

  • Patient registration and search
  • Test orders and accession numbers
  • Printable sample labels

Workflow illustrations. Your demonstration will use the NordLIS application.

Scene 1 of 4: Register and order

04 · Quality and accountability

Checks before release.
A record after it.

Quality depends on the decisions made at each step. NordLIS gives your team explicit review stages and a history of recorded actions.

Review before acceptance

Incoming analyzer results enter a staging queue. Unmapped results are held for resolution, and QC observations stay separate from patient-result acceptance.

Controlled result release

Release permissions follow user roles and laboratory sections. Reviewers can inspect reference ranges and flags before releasing results.

Traceable corrections

Corrections after release require a reason. Audit events record the action and actor, and result versions retain the previous values.

Tested interface behavior

Our engineering checks include analyzer-message replay, mapping checks, and rejection cases. Site acceptance confirms the behavior of your configured connections.

05 · Implementation with LabSolution

Built around your laboratory. Verified with your team.

Start with your test menu, instruments, review responsibilities, and report formats. Agree the configuration and acceptance criteria before go-live.

  1. Configuration

    Define how NordLIS should reflect your laboratory’s workflows and reporting needs.

  2. Deployment

    Agree hosting, access, and environment arrangements for your installation.

  3. Interface validation

    Agree how to test each connection and what it must pass.

  4. Training

    Plan training around the tasks each laboratory role needs to perform.

  5. Support

    Confirm support arrangements and responsibilities before go-live.

Your NordLIS demonstration

See your laboratory’s workflow in NordLIS.

Plan a walkthrough of patient registration, analyzer intake, standards mapping, and result release with LabSolution.

Prepare and download an enquiry draft. This website does not send or store enquiries.