<?xml version="1.0" encoding="UTF-8"?>

<NamingSystem xmlns="http://hl7.org/fhir">
  <id value="patient-mrn-naming-system"/>
  <text>
    <status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: NamingSystem patient-mrn-naming-system</b></p><a name="patient-mrn-naming-system"> </a><a name="hcpatient-mrn-naming-system"> </a><h3>Summary</h3><table class="grid"><tr><td>Defining URL</td><td>https://fhir.senaite.org/NamingSystem/patient-mrn-naming-system</td></tr><tr><td>Version</td><td>0.1.0</td></tr><tr><td>Name</td><td>SenaitePatientMrn</td></tr><tr><td>Title</td><td>SENAITE Patient MRN Namespace</td></tr><tr><td>Status</td><td>draft</td></tr><tr><td>Definition</td><td><div><p>Default namespace for the external Patient ID — the consumer-owned business identifier for a patient, being the Medical Record Number. Carried as identifier[mrn] (use = #secondary) on SenaitePatient and may be supplied on create. Both the slice and this namespace URI are named for the MRN field in SENAITE rather than for the generic pattern. A consumer will normally supply its own registry URI here, agreed at integration time; this URI is the default for deployments and consumers that have none. A system is mandatory either way, because request.ifNoneExist and the identifier search parameter match on system and value and ignore Identifier.use. Note that this default is a shared namespace: it must not be relied on where more than one consumer submits to the same SENAITE instance, since two consumers using the same MRN value would then match each other.</p>
</div></td></tr><tr><td>Publisher</td><td>Naralabs</td></tr></table><h3>Identifiers</h3><table class="grid"><tr><td><b>Type</b></td><td><b>Value</b></td><td><b>Preferred</b></td><td><b>Comment</b></td></tr><tr><td>URI</td><td>https://fhir.senaite.org/NamingSystem/patient-mrn</td><td>true</td><td>Default MRN namespace for Patient. Deployment-configurable; the URI mirrors the mrn slice name.</td></tr></table></div>
  </text>
  <url value="https://fhir.senaite.org/NamingSystem/patient-mrn-naming-system"/>
  <version value="0.1.0"/>
  <name value="SenaitePatientMrn"/>
  <title value="SENAITE Patient MRN Namespace"/>
  <status value="draft"/>
  <kind value="identifier"/>
  <date value="2026-01-01"/>
  <publisher value="Naralabs"/>
  <contact>
    <name value="Naralabs"/>
    <telecom>
      <system value="url"/>
      <value value="https://naralabs.com"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="info@naralabs.com"/>
    </telecom>
  </contact>
  <contact>
    <name value="Senaite FHIR"/>
    <telecom>
      <system value="email"/>
      <value value="info@naralabs.com"/>
      <use value="work"/>
    </telecom>
  </contact>
  <description value="Default namespace for the external Patient ID — the consumer-owned business identifier for a patient, being the Medical Record Number. Carried as identifier[mrn] (use = #secondary) on SenaitePatient and may be supplied on create. Both the slice and this namespace URI are named for the MRN field in SENAITE rather than for the generic pattern. A consumer will normally supply its own registry URI here, agreed at integration time; this URI is the default for deployments and consumers that have none. A system is mandatory either way, because request.ifNoneExist and the identifier search parameter match on system and value and ignore Identifier.use. Note that this default is a shared namespace: it must not be relied on where more than one consumer submits to the same SENAITE instance, since two consumers using the same MRN value would then match each other."/>
  <uniqueId>
    <type value="uri"/>
    <value value="https://fhir.senaite.org/NamingSystem/patient-mrn"/>
    <preferred value="true"/>
    <comment value="Default MRN namespace for Patient. Deployment-configurable; the URI mirrors the mrn slice name."/>
  </uniqueId>
</NamingSystem>