10. 1. 3. accessRight
Description: access right
Omission: not allowed
Repetition: allowed. The element
should be repeated the number of times access rights are set up. At least,
it is essential to set up an access right for creators so that they will not
be rejected from making a reference.
If multiple accessRight
elements exist, the accessRight elements are mutually under the “OR”
condition. When more than two subordinate elements of a facility, medical
department, occupation, or person exist to a single accessRight element, the
condition is “AND”. If nothing meets this “AND” condition,
the access right is not accepted.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
permit
|
string
|
#REQUIRED
|
MML0034
|
Rights of reference
none: no access permissible
read: reference permissible
write: reference and correction
permissible
delete: reference and deletion
permissible
all: reference, correction, and
deletion permissible
|
|
startDate
|
date
|
#IMPLIED
|
|
Start date of an access
right
|
|
endDate
|
date
|
#IMPLIED
|
|
End date of an access
right
|
In order to specify explicitly that
no reference is permissible, set none for the permit attribute.
Answers to a deletion request for
deletion-permissible documents are not specifically defined in MML. When it
is important to keep the correction history of a medical record, it is an
assumable way during implementation to keep the document invisible to normal
accesses rather than carrying out physical deletion.
10.1.3.1 mmlSc:facility
Description: facility. Set up
access rights in the facility unit.
Omission: allowed
10.1.3.2 mmlSc:facilityName
Description: facility name
Data type: string
Omission: not allowed
Repetition: allowed. The element
should be repeated the same number of times as the number of facilities
for which access rights are set.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
mmlSc:facilityCode
|
string
|
#REQUIRED
|
MML0035
|
Facility access right
definition
|
|
mmlSc:tableId
|
string
|
#IMPLIED
|
|
Table name used for
the facility access right definition. Enter MML0035.
|
|
mmlSc:facilityId
|
string
|
#IMPLIED
|
|
Facility code
|
|
mmlSc:facilityIdType
|
string
|
#IMPLIED
|
MML0027
|
Facility code master
name
|
Meanings
of each value in the facility access right definition are as follows:
|
all
|
All accessing facilities are
permissible.
|
|
creator
|
The same facilities as those
of creators are permissible.
|
|
experience
|
Facilities that have the experience
of medical cares to a described person (patient) are permissible.
The method of selecting a facility that has the experience of medical
cares is subject to each application.
|
|
individual
|
Facilities with facility IDs
that are individually specified are permissible.
Permissible facilities are specified in the mmlSc:facilityId and mmlSc:facilityIdType.
|
10.1.3.3 mmlSc:department
Description: medical department
Omission: allowed
10.1.3.4 mmlSc:departmentName
Description: medical department name
Omission: not allowed
Repetition: allowed. The element
should be repeated the same number of times as the number of departments
for which access rights are set.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
mmlSc:departmentCode
mmlSc:tableId
|
string
string
|
#REQUIRED
#IMPLIED
|
MML0028
|
Medical department
code
Table name of the medical
department code. Enter MML0028.
|
10.1.3.5 mmlSc:licence
Description: occupation
Omission: allowed
10.1.3.6 mmlSc:licenceName
Description: occupation name
Omission: not allowed
Repetition: allowed. The element
should be repeated the same number of times as the number of occupations
for which access rights are set.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
mmlSc:licenceCode
mmlSc:tableId
|
string
string
|
#REQUIRED
#IMPLIED
|
MML0026
|
Occupation code
Table name of the occupation
code. Enter MML0026.
|
10.1.3.7 mmlSc:person
Description: person
Omission: allowed
10.1.3.8 mmlSc:personName
Description: person's name
Data type: string
Omission: not allowed
Repetition: allowed. The element
should be repeated the same number of times as the number of people for
which access rights are set.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
mmlSc:personCode
|
string
|
#REQUIRED
|
MML0036
|
Personal access right
definition
|
|
mmlSc:tableId
|
string
|
#IMPLIED
|
|
Table name used for
the personal access right definition. Enter MML0036.
|
|
mmlSc:personId
|
string
|
#IMPLIED
|
|
Personal ID
|
|
mmlSc:personIdType
|
string
|
#IMPLIED
|
|
Personal ID master
name
|
Meanings
of each value in the personal access right definition are as follows:
|
all
|
All accessing people are permissible.
|
|
creator
|
Creators are permissible.
|
|
patient
|
Described persons (patients)
themselves are permissible.
|
|
individual
|
Persons with personal IDs
that are individually specified are permissible.
Permissible persons are specified in the mmlSc:personId and mmlSc:personIdType.
|
Example: Description of 1.2.1.1.1.securityLevel
(type of access right)
Case to set up an access right
of reference, correction, and deletion from October 1, 2001 to December 31,
2001 for doctors at the internal medicine department, Miyazaki Medical College
Hospital.
<securityLevel>
<accessRight
permit="all"
startDate="2001-10-01"
endDate="2001-12-31">
<mmlSc:facility>
<mmlSc:facilityName
mmlSc:facilityCode="individual"
mmlSc:tableId="MML0035"
mmlSc:facilityId="JPN453010100003"
mmlSc:facilityIdType="JMARI">
Miyazaki Medical College Hospital
</mmlSc:facilityName>
</mmlSc:facility>
<mmlSc:department>
<mmlSc:departmentName
mmlSc:departmentCode="01"
mmlSc:tableId="MML0028"/>
</mmlSc:department>
<mmlSc:licence>
<mmlSc:licenceName
mmlSc:licenceCode="doctor"
mmlSc:tableId="MML0026"/>
</mmlSc:licence>
</accessRight>
</securityLevel>
Case to set up an open-ended access
right of all for the creator’s facility and an access right of reference
from October 1, 2001 to December 31, 2001 for a patient Taro Kanja.
<securityLevel>
<accessRight
permit="all">
<mmlSc:facility>
<mmlSc:facilityName
mmlSc:facilityCode="creator"
mmlSc:tableId="MML0035">
Creator’s facility
</mmlSc:facilityName>
</mmlSc:facility>
</accessRight>
<accessRight
permit="read"
startDate="2001-10-01"
endDate="2001-12-31">
<mmlSc:person>
<mmlSc:personName
mmlSc:personCode="patient"
mmlSc:tableId="MML0036"
mmlSc:personId="4500001234"
mmlSc:personIdType="dolphinUserid_2001-10-03">
Taro Kanja
</mmlSc:personName>
</mmlSc:person>
</accessRight>
</securityLevel>
10.1.3.9 title
Description: document title
Data type: string
Omission: not allowed
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
generationPurpose
|
string
|
#IMPLIED
|
MML0007
|
Document type in detail
|
10.1.3.10 docId
Description: document ID information
Omission: not allowed
10.1.3.11 uid
Description: document unique
ID. The format of unique numbers should be UUID. (UUID is a format that
includes hyphens.) It is strongly recommended that the MML processor should
somehow locally store the uid when it receives an MML instance.
Data type: string
Omission: not allowed
Example:
<uid>0aae5960-667c-11d3-9751-00105a6792e7</uid>
10.1.3.12 parentId
Description: related parent document
ID. For usage, refer to the “Link of documents” section in the
basic policy.
Data type: string
Omission: allowed
Repetition: allowed. If multiple
parent documents are available, the element should be repeated.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
relation
|
string
|
#IMPLIED
|
MML0008
|
Document relation type
|
Example: When a document is a revised
document(new edition) of a parent document
<parentId relation = "oldEdition">0aae5960-667c-11d3-9751-00105a6792e8</parentId>
10.1.3.13 groupId
Description: group ID. For usage,
refer to the “Link of documents using the groupId” section in the
basic policy.
Data type: string
Omission: allowed
Repetition: allowed. If a document
belongs to multiple groups, the element should be repeated.
Attribute:
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
groupClass
|
string
|
#IMPLIED
|
MML0007
|
Module group type
|
10.1.3.14 confirmDate
Description: date and time when
the electronic storage of a medical chart is comfirmed
Data type: dateTime Format: CCYY-MM-DDThh:mm:ss
Omission: not allowed
Attribute: When time series information
is one document, specify the start/end dates and times in the following
attributes. Note that scopePeriod (1.1.4.) represents the period covered
by an entire MML document and that in contrast, this represents the period
of one <paragraph>.
|
Attribute name
|
Data type
|
Omission
|
Table
|
Remarks
|
|
start
|
dateTime
|
#IMPLIED
|
|
Start date and time
for time series information
|
|
end
|
dateTime
|
#IMPLIED
|
|
End date and time for
time series information
|
|
firstConfirmDate
|
dateTime
|
#IMPLIED
|
|
The first confirmed
date when a correction has been made.
|
|
eventDate
|
dateTime
|
#IMPLIED
|
|
Date and time of a
described medical event
|
10.1.3.15 mmlCi:CreatorInfo
Description: creator information
of individual document. Refer to the MML common format (Creator information
format) for the structure.
Omission: not allowed
10.1.3.16 extRefs
Description: list of all external
link information described in the content. The list of external reference
files can be obtained without analyzing the content.
Omission: not allowed
10.1.3.17 mmlCm:extRef
Description: external link information.
Refer to the MML common format (External reference format) for the structure.
Omission: allowed
Repetition: allowed. The element
should be repeated the same number of times as the number of external link
information.
© 2003. All rights reserved