HL7 Table HL70360: Degree / Licence / Certificate

HL70360 enumerates the academic degrees, professional licences, and certifications that follow a clinician's name — the MD, RN, PhD, PA, BSN strings that providers attach to their signature. It lives in XCN.21 Professional Suffix, in PRA-6 Specialty (Practitioner Detail), and in the STF (Staff Identification) master-file segment. HL70360 is one of the larger published HL7 tables — well over fifty codes — and it is user-defined, so most sites carry additional local entries for credentials that the standard does not enumerate.

Purpose

HL70360 lets sending systems communicate a clinician's earned credentials in a way that receiving systems can render on screens, badge prints, audit logs, and orders. Beyond display, the code is used by some downstream systems to gate ordering privileges (only MD and DO may sign certain order classes) and to populate provider directories. The table mixes academic degrees (BA, MS, PhD), clinical doctorates (MD, DO, PharmD), licences (RN, NP, PA), and certifications (EMT, RMA, CER) inside a single namespace, which is a frequent source of mapping ambiguity.

Where it's used

• XCN.21 Professional Suffix — the canonical home of HL70360 on every XCN-typed provider name field (OBR-16, OBR-32, ORC-12, PV1-7, etc.).
• PRA-6 Practitioner Detail — degree, licence, and certification on master-file practitioner records.
• STF-26 Degree — staff master-file degree.

Code list

The published HL70360 set is larger than the subset shown above; additional codes exist for foreign credentials (e.g., FCCP, FRCS) and historical academic titles. Local sites routinely add codes for state-specific certifications.

Code system OID

• OID: 2.16.840.1.113883.18.255
• Canonical URI: http://terminology.hl7.org/CodeSystem/v2-0360

The OID resolves on the HL7 Terminology server and is the value Vorro emits in CWE.14 / XCN.22 (Assigning Jurisdiction) when downstream profiles demand OID-bound coded credentials.

HL7-defined vs user-defined

HL70360 is user-defined. The standard publishes a large suggested set, but explicitly allows sites to add local credentials, retire codes that are not relevant, and override displays for region-specific naming. In practice every HIS vendor ships a slightly different starter set, and the same RN-equivalent credential may travel as RN, RN., R.N., or a vendor-internal numeric code across the same hospital system.

Version differences

• v2.3 — Table introduced with a small set focused on U.S. degrees (MD, DO, RN, BS, MS, PhD).
• v2.4 – v2.5 — Expanded to include PA, NP, EMT, and a wider band of allied-health credentials.
• v2.6 — Added pharmacy (PharmD, RPH) and dental credentials.
• v2.7 — XCN.21 widened from IS to allow CWE-style metadata in adjacent fields; OID binding became practical.
• v2.8 – v2.8.1 — Additional international degree codes added; published set stabilized.

Common mistakes

• Treating the credential string as free text — sending MD, FACP as a single XCN.21 value. XCN.21 carries one HL70360 code; multiple credentials use repetitions (MD~FACP).
• Confusing case for PharmD. The published code is mixed-case; engines that uppercase-normalize on ingest will produce PHARMD, which is not the published value and will fail strict ConceptMap lookup.
• Mapping RN onto FHIR Practitioner.qualification.code without the system URI. Downstream FHIR consumers cannot disambiguate site-local RN from HL70360 RN without the system binding.
• Rejecting unknown credentials. HL70360 is user-defined; receivers must accept site-local codes and surface them for curation rather than NAK.
• Confusing degree (MD) with provider role (Attending). HL70360 is what the provider is; HL70443/HL70912 is the role the provider plays on a given encounter.

Examples

An XCN with both first credential (RN) and a stacked credential (BSN):

ORC|RE|||||||||4567^JONES^MARY^L^^^^^NPI^L^^^NPI^^^^^^^RN~BSN

A physician with MD:

PV1|1|I|3West^301^A^MAIN||||1234^SMITH^JOHN^A^^^^^NPI^L^^^NPI^^^^^^^MD

Same MD value translated to a FHIR Practitioner.qualification snippet:

{
  "resourceType": "Practitioner",
  "id": "1234",
  "qualification": [{
    "code": {
      "coding": [{
        "system": "http://terminology.hl7.org/CodeSystem/v2-0360",
        "code": "MD",
        "display": "Doctor of Medicine"
      }]
    }
  }]
}

Mapping failure example — vendor credential:

PV1|1|I|3West^301^A^MAIN||||1234^SMITH^JOHN^A^^^^^NPI^L^^^NPI^^^^^^^MD-X

MD-X is not in HL70360. A conformant engine preserves the raw value, emits the FHIR Coding with system http://terminology.hl7.org/CodeSystem/v2-0360 and code: MD-X, and queues the value for terminology curation. It must not silently rewrite MD-X to MD.

FHIR mapping

The v2-to-FHIR IG does not publish a ConceptMap for this table; the mapping below follows the obvious correspondence, preserving HL70360 codes as the Coding.code on Practitioner.qualification.code with system http://terminology.hl7.org/CodeSystem/v2-0360. Unlike HL70001 (where six codes collapse to four), HL70360 has no semantic collapse — every v2 code becomes a distinct FHIR coding. The only normalization the ConceptMap does is fixing display strings.

Engine considerations

• Case preservation — Do not uppercase-normalize on ingest; PharmD is mixed-case as published. Normalize only known case-variant aliases via explicit mapping.
• Repetition handling — XCN.21 may repeat (MD~FACP~FACC). Engines must split on repetition delimiter and map each code independently.
• User-defined — never NAK — Receivers must accept site-local credentials and route unknowns to curation.
• FHIR system binding — Always emit system=http://terminology.hl7.org/CodeSystem/v2-0360 when the code is from the published set; use a local system URI for site extensions so consumers can distinguish.

How Vorro handles HL70360

Vorro accepts any XCN.21 value, preserves case, splits on repetition, and looks up each component in a per-source mapping table. Codes that match the published HL70360 set are tagged with the canonical OID and flow through to downstream channels. Site-local codes are tagged with a per-source system URI and flow through untouched, with a curation surface so an administrator can either bind the local code to a published HL70360 entry or accept it as a permanent site extension.

On outbound, Vorro emits HL70360 as IS for v2.5 and earlier profiles and as part of CWE-rich XCN structures for v2.7+ destinations. The original raw credential string is always preserved so that round-tripping FHIR Practitioner.qualification back to v2 does not lose precision.

Related pages

• XCN data type — Extended Composite ID Number and Name for Persons
• STF segment — Staff Identification
• HL70443 code table — Provider Role

Sources

• HL7 Terminology — CodeSystem v2-0360 Degree/License/Certificate
• HL7 v2 product brief