This page is part of the FHIR Specification (v1.4.0:
STU
3 Ballot 3). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions
This is the narrative for the resource. See also the
XML
or
or
JSON
format.
format. This example conforms to the
profile OperationDefinition
.
Generated
Narrative
with
Details
Generated Narrative with Details
id
:
patient-mpi
: patient-mpi
url
:
:
http://hl7.org/fhir/OperationDefinitino/patient-mpi
name
:
Patient
MPI
(Multiple
Patient
Index)
search
: Patient MPI (Multiple Patient Index) search
status
:
draft
: draft
kind
:
query
: query
experimental
:
false
: false
date : 18/08/2015
publisher
:
HL7,
Inc
: HL7, Inc
| - | Telecom |
| * | http://hl7.org/fhir |
date
:
18/08/2015
description
:
An
MPI
search
differs
from
a
normal
search
because
the
parameters
are
interpreted
as
inputs
to
an
MPI
match
process,
rather
than
as
direct
match
criteria
on
the
returned
resources
: An MPI search differs from a normal search because the parameters are interpreted as inputs to an MPI match process, rather than as direct match criteria on the returned resources
requirements
:
This
query
is
defined
to
allow
an
MPI
to
be
integrated
in
a
FHIR
server
environment,
and
to
allow
a
client
to
delegate
the
matching
process
to
a
specialist.
MPI
algorithms
are
often
highly
tailored
to
a
particular
patient
set
: This query is defined to allow an MPI to be integrated in a FHIR server environment, and to allow a client to delegate the matching process to a specialist. MPI algorithms are often highly tailored to a particular patient set
idempotent
:
true
: true
code
:
mpi
: mpi
notes
:
All
the
standard
search
parameters
apply,
and
are
interpreted
as
inputs
to
the
MPI
algorithm.
The
_sort
parameter
is
not
used.
Matches
are
returned
in
order
of
highest
match
to
lowest
match,
with
both
a
%
in
the
score,
and
an
asessement
of
the
match
using
the
extension
http://hl7.org/fhir/StructureDefinition/patient-mpi-match
comment
: All the standard search parameters apply, and are interpreted as inputs to the MPI algorithm. The _sort parameter is not used. Matches are returned in order of highest match to lowest match, with both a % in the score, and an asessement of the match using the extension http://hl7.org/fhir/StructureDefinition/patient-mpi-match
system
:
false
: false
type
:
Patient
: Patient
instance
:
false
: false
parameter
name
: userid: useriduse
: in: inmin
: 0: 0max
: 1: 1documentation
: User identity for the MPI to consider when creating a return set. This paraemter is defined in the assumption that the MPI ay be a separate module from other FHIR Servers, with a trust relationship to it. Actualy deployment scenarios will determine whether this parameter is used: User identity for the MPI to consider when creating a return set. This paraemter is defined in the assumption that the MPI ay be a separate module from other FHIR Servers, with a trust relationship to it. Actualy deployment scenarios will determine whether this parameter is usedtype
: string: string
parameter
name
: result: resultuse
: out: outmin
: 0: 0max
: *: *documentation
: Patients that match this MPI query: Patients that match this MPI querytype
: Patient: Patient
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.