Chart Map
Maps every MEDCIN finding in a patient chart to other medical vocabularies in a single request — the batch, whole-encounter counterpart to the single-code TranslateItem endpoint. Given a chart containing an encounter and its findings, the ChartMap API (POST /Quippe/Coding/ChartMap) translates each finding to the requested target vocabularies (ICD-10, ICD-9-CM, SNOMED CT, CPT, LOINC, and others) and returns the matching codes with their relationship to the source finding.
Common uses include coding an entire encounter for billing or reporting, batch terminology mapping of structured notes, and generating a problem/claim code set from documented findings.
POST /Quippe/Coding/ChartMap
Use this endpoint to map many findings in a patient chart at once. To map a single code instead, use [/Quippe/Coding/TranslateItem](/api-reference/rest/get-quippe-coding-translate-item). The chart this consumes is typically produced upstream from an existing, structured Patient chart or from free text by [/Quippe/TextRecognition/Recognize](/api-reference/rest/post-quippe-text-recognition-recognize).
Authentication
AuthorizationBasic
Login and password used to access quippe.medicomp.com. On-premise Quippe deployments can be configured to use whatever authentication and authorization your application is configured for, so basic authentication is used here to access the Quippe sandbox and is not a product requirement.
OR
AuthorizationBearer
JSON web token generated by a request to the /Quippe/Security/Token web service endpoint in Quippe.
Query parameters
DataFormat
Specifies how objects are encoded in the output
Allowed values:
RequestId
Optional value that can be used by clients to track multiple requests.
Culture
Culture to use when handling the request. If not specified the default value configured on the server will be used.
Request
This endpoint expects an object.
Chart
The patient chart to map, as XML or JSON (use InputFormat to declare which, or leave blank to auto-detect). Sent as a form field in the request body. The chart contains an Encounter (with an EncounterTime attribute) whose Records hold the findings to map. Each Record supports the attributes id, MedcinId, Prefix, Result, Modifier, Status, Value, Unit, Onset, Duration, Episode, and Note; MedcinId identifies the finding to translate and the others carry its qualifiers. If the chart includes a Patient id, patient age and sex are resolved and used as translation context.
Vocabs
Comma-separated list of target vocabulary codes to map each finding into (for example icd10, snomed, cpt). When omitted, a default set of vocabularies is used. The full list of supported vocabulary codes can be retrieved from the [/Quippe/Coding/Vocabs](/api-reference/rest/get-quippe-coding-vocabs) endpoint.
IncludeHints
Indicates whether textual coding hints for the target codes should be included with the code mapping results, if available.
IncludeSpecifierLists
Indicates whether code specifier lists associated with the target codes should be included with the code mapping results, if available.
AutoGenerateMaps
Indicates whether maps from qualified MEDCIN concepts should be automatically generated where applicable if no maps are available.
MapExpressionOption
Indicates how optional SNOMED-CT map expressions are created. Possible values are FullDescription (map expression include thes full description with sematic tag), NoDescription (map expresion should not include the description), or NoSemanticTag (map expression should include the description, but no sematic tag) Only affects SNOMED-CT targets.
Allowed values:
InputFormat
The MIME type of the Chart input, for example “application/vnd.medicomp.quippe.note+xml” for Quippe note XML. Leave blank (default) to deduce the format from the content.
Response
Successful response
codeMap
Errors
401
Unauthorized Error
500
Internal Server Error