CLAIM is a partial structure that is inserted in the MML basic structure. In this section the MML basic structure will be described as cited from Version 2.3 of the MML specifications. In addition, CLAIM-specific definitions, comments, and precautions will be described under the item [CLAIM].
1. Mml
[Detail] MML start/end tag
[CLAIM] The namespaces declaration of the CLAIM module must be inserted as an attribute. Other namespaces declarations can also be included for the utilized DTD only.
The uri shown below must be used for the namespaces declaration. At the present time, however, DTD, for example, does not exist at the uri below. The uri combines the declarations of versions in module units. (See "Version control in module units" in the "Basic policy" section of these specifications.)
uri of appointment request module
http://www.medxml.net/claim/claimModule/2.1
uri of point/monetary amount module
http://www.medxml.net/claim/claimAmountModule/2.1
1.1. MmlHeader
[Detail] Header information
1.1.1.mmlCi:CreatorInfo
[Detail] Creator identification information. Refer to the MML common format (creator information format) for the structure.
[CLAIM] Creator information that is generated during MML instance creation. Does not have to be matched to the CLAIM module's creator.
[Omission] Not allowed
1.1.3.1. tocItem
[Detail] All DTDs used in this MML document are listed.
[CLAIM] The utilized DTD must include a uri that indicates the CLAIM module DTD. The uri's of CLAIM Version 2.1 are shown below. Even if the engineer places a copy of the CLAIM module DTD in the local directory, the formal uri's shown below must be entered.
uri of appointment request module
http://www.medxml.net/claim/claimModule/2.1
uri of point/monetary amount module
http://www.medxml.net/claim/claimAmountModule/2.1
[Data type] string
[Omission] Not allowed
[Repetition setting] Repeated. The data should be repeated for the number of DTDs used.
1.2.1.1. docInfo
[Detail] Individual document header information
[CLAIM] MML0005 table's "claim" and "claimAmount" are used. For the contentModuleType, "claim" must be input for the appointment request module, and "claimAmount" for the point/monetary amount module.
[Omission] Not allowed
[Attribute]
AttributeName DataType Omission TableUsed Explanation
contentModuleType string #IMPLIED MML0005 Document type code
1.2.1.1.2. title
[Detail] Document title
[CLAIM] The necessity of including the document title in the CLAIM module is not evident. But since it cannot be omitted, some sort of document title must be included. Here is a conceivable example of a title: automatically incorporate the name of the medical care action classification that appears first.
"claim" must be input for the attribute "generationPurpose."
[Data type] string
[Omission] Not allowed
[Attribute]
AttributeName DataType Omission TableUsed Explanation
generationPurpose string #IMPLIED MML0007 Type of document detail
1.2.1.1.3.1. uid
[Detail] Document unique ID. The format of the unique number should be UUID. (UUID should include hyphens.) It is strongly recommended that the MML processor save the uid locally with some measure when the MML instance is received.
[CLAIM] A document unique ID is required even in the CLAIM module.
[Data type] string
[Omission] Not allowed
[Example]
<uid>0aae5960-667c-11d3-9751-00105a6792e7</uid>
1.2.1.1.3.2. parentId
[Detail] ID of related parent document. For usage, refer to "Link of documents" in the basic policy.
[CLAIM] It is assumed that this is used in a CLAIM module to record the correlation to the order document. In short, "order" is input into the attribute "relation" with the order document (Progress course information module that includes the order) used as the related parent document.
Also, the uid of the related health insurance information module can be set up with the parentId as well. In principle, however, it should be recorded in claim:insuranceUid in the CLAIM module.
[Data type] string
[Omission] Omission allowed
[Repetition setting] Repeated. If multiple parent documents are available, the data should be repeated.
[Attribute]
AttributeName DataType Omission TableUsed Explanation
relation string #IMPLIED MML0008 Type of relation
[Example] When the document is corrected (new edition) for the parent document
<parentId relation = "oldEdition">0aae5960-667c-11d3-9751-00105a6792e8</parentId>
1.2.1.1.4. confirmDate
[Detail] Confirmed date of medical chart electronic storage
[CLAIM] This is the module creation date. It does not necessarily have to be the same as the order issuance date, expected performance date, and performance date in the CLAIM module.
[Data type] date Form: CCYY-MM-DD
[Omission] Not allowed
[Attribute] When time series information is one document, input the start date and the end date in the next attribute. ScopePeriod (1.1.4.) represents the coverage period for the entire MML document. In contrast, this represents the period of one MmlModuleItem.
Attribute name
Data type
Omission
Table used
Explanation
0
0
0
0
0 0
0
0
0
0
start date #IMPLIED Start date for time series information
end date #IMPLIED End date for time series information
1.2.1.1.5.mmlCi:CreatorInfo
[Detail] Creator information of individual document. Refer to the common format (creator information format) for the structure.
[CLAIM] Most likely, the CLAIM document creator is the doctor who indicated the medical care action that is entered.
[Omission] Not allowed
1.2.1.1.6.extRefs
[Detail] List of all external link information described in the content. The list of external reference files can be obtained without analyzing the content.
[CLAIM] Since there is no mmlCm:extRef element in the CLAIM module, extRefs is set up as a dummy element.
[Omission] Not allowed
1.2.1.1.6.1.mmlCm:extRef
[Detail] External link information. Refer to the MML common format (external reference format) for the structure.
[CLAIM] Since there is no mmlCm:extRef element in the CLAIM module, mmlCm:extRef is omitted.
[Omission] Omission allowed
[Repetition setting] The data should be repeated for the number of external link information described.
1.2.1.2.content
[Detail] Content. Input the module using namespace. Only one type of module can be input in one content.
[CLAIM] Only one CLAIM module is inserted into one content.
[Omission] Normally omission is not allowed. Omission is allowed only for response to the list format query.